-
Notifications
You must be signed in to change notification settings - Fork 712
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
Timeout reads and writes in the http server. #1917
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May need to adjust the timeouts in common/xfer/websocket.go
as well, probably?
Ah yes websockets! On Wednesday, 12 October 2016, Paul Bellamy [email protected]
|
Won't this interact badly with persistent http connections? |
@tomwilkie Out of curiosity, how have you confirmed that this fixes #1916 ? |
Handler: handler, | ||
ReadTimeout: httpTimeout, | ||
WriteTimeout: httpTimeout, | ||
MaxHeaderBytes: 1 << 20, |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
And I am still waiting for an answer to my question re persistent connections. |
I'm attempting to reproduce locally. So far what I've tried: making a connection which hangs (stops sending data) during the sending of a POST body. This causes goroutine count to rise until those connections are closed on the client side, at which point they drop again. |
ok, good news and bad news. |
Disregard the bad news above, it's an unrelated problem with my local setup since it's happening on master too (when accessing via /admin/scope). Connecting to scope.kube-system directly works fine with this PR. |
ok, i'm now confident in my testing:
|
Fixes #1916