-
Notifications
You must be signed in to change notification settings - Fork 18k
net/http, x/net/http2: small delays trigger timeout #61545
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Detailed explanation of the issue: HTTP2 response delayed more than 5 sec by introducing a network delay of just 100 ms I am writing a high performance http2 client and server applications. I have observed that client's VM is not able to transmit the packet in time to network. Only 100 ms delay was introduced, but transmitting out the http2 request is taking way too much of time (>5 sec). Delay was introduced using below command: I observed the goroutines, here is the summary where most of time time went:
I also tried to increase the outgoing buffer as below (at client side): http2Transport.AllowHTTP = true // So http2.Transport doesn't complain the URL scheme isn't 'https' conn = &Client{ But, with this change, the connection are not coming up, giving below error: goroutine 10374884 [select]: goroutine 10379533 [select]: goroutine 28 [IO wait]: |
it seems more likely you misconfigured tc? |
Thank you very much, it was really 'limit' option of 'tc' command, without which messages were clogged. I tried with 'limit' option and it worked as expected. |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
Http2 requests, with timeout value 5 sec should not be timed out (i.e. response should be received within 5 sec) on introducing a delay of 100ms (or even more, upto around 4 sec) on local VM or in network.
What did you see instead?
Http2 requests (with response wait timer value 5 sec ) are timed out on introducing a delay of 100ms (on local VM).
Even, below settings are not working as expected:
http.Transport -> WriteBufferSize and ReadBufferSize
The text was updated successfully, but these errors were encountered: