Receive: race condition in handler Close() when stopped early #7087
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.
Receiver hangs waiting for the HTTP Handler to shutdown if an error occurs before Handler is initialized. This might happen, for example, if the hashring is too small for a given replication factor.
Changes
Fixes a race condition in
receive.Handler.Close()
.Verification
Before this change, the race condition could be reproduced with the script below. Eventually (in about 1-2 seconds) receiver would be able to start "successfully" and the script would hang until killed with SIGKILL. Health checks would not work since the health check listener is already down.