Fixed bug in client comms. #1423
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When the client received a 503 status from the server (due to load shedding for example) it failed to close the socket on error paths. This resulted in a leak of a socket and presented in having many TIME_WAIT sockets. This PR refactors the http comms code to ensure the socket is closed on all error paths
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the client received a 503 status from the server (due to load
shedding for example) it failed to close the socket on error
paths. This resulted in a leak of a socket and presented in having
many TIME_WAIT sockets.
This PR refactors the http comms code to ensure the socket is closed
on all error paths