shinrich commented on issue #8199: URL: https://github.com/apache/trafficserver/issues/8199#issuecomment-907274212
I am running into this with a heavily used Http2 sessions between to ATS boxes in the HTTP/2 to origin work. For both POST bodies and response bodies. Unlike the case of ATS communicating with a dedicated client (web browser), these are unrelated stream requests scheduled onto a common HTTP/2 session. If the stream and session are set to the same value, each stream will push through until it finishes or exhausts the stream (and session) window. I agree that just opening up the current initial_window_size_in wide will address the issue by more or less eliminating the windowing logic. However, by having a larger session window, you could have multiple streams make progress (exhausting their stream windows in the process). In my debugging where I added logic printing session/stream windows at the exhaustion point, the ATS implementation would always stop with session window at 0. Sometimes stream window was also at 0, but generally not. Looking at numbers from our non-ATS peer, it was not uncommon to see higher session window sizes than stream window sizes (i.e., the stream exhausts before the session window is exhausted). Of course having a larger stream window than session window does not make sense for all cases, but I think it is a useful distinction for some cases. In the outbound case, we may in fact want to make these window size settings overridable, so we can tune them for specific origins.. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
