GO_AWAY and Server closing the connection due MaxConcurrentStreams

[MunteanuAndreiStefan]

ValueOrError`1:Error occured on loading ImageMeta entities from the collection 'XXX', url: https://XXX/api/meta/collections/XXX-YYY-ZZZ-
Error: Server closing the connection! Error code: NO_ERR...;

When I have more than 10 MaxConcurrentStreams and try to download 1000+ files, I get GO_AWAY.

Is there a mechanism to retry it from where it failed? Should I manually setup something before start making the requests?
I've tested with HTTP/1.1 it works all right with 20 max connections. Any idea/direction?

[Benedicht]

In case of HTTP/2, the requests are put into the HTTP/2 handler's queue and the timer starts ticking. However, the HTTP/2 has its own max concurrent stream and number of requests to handle through the connection's lifetime.
With HTTP/2 you can orgenize a custom queue on top of the plugin. I'm also going to fix it in the next big release.

[Benedicht]

Currently processed requests are retried depending on their retry settings. Requests in the HTTP/2 queue will be retried without consuming a retry attempt.