akka-http 10.2.10 seems to have changed the semantics of the max-open-requests host connection pool configuration

[jphelp32]

Change #4132 in 10.2.10 seems to have changed the semantics of the host connection pool max-open-requests configuration. Consider that N requests to a single host are accepted by Http().singleRequest() before a BufferOverflowException occurs. Prior to the mentioned change, N = max-open-connections. Now after this change, it appears that N = max-open-requests + max-connections. I've inquired about this #here. Is this a regression? or an intended behavior change?

[johanandren]

Looks like it indeed may have been an unintended consequence of the fix in #4132

[jphelp32]

@johanandren do you expect this to be fixed in any future 10.2.x release?

[johanandren]

No, if we address this, I expect that it will be for the upcoming 10.4 series.

I understand it is annoying with this regression but we will only consider doing additional 10.2.x releases if critical or security issues is found.