don't announce stopped-event to websocket trackers. #5933
Merged
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.
This (appears) to solve a shutdown stall where we send stopped-announces after aborting outstanding announces (including the persistent websocket connection). The announec causes the persistent connection to be re-established and sometimes not torn down properly again, to complete the shut down.
Without this patch shutdown can stall, waiting for these async operations:
@paullouisageneau Does this make sense? I fear I may have misunderstood something. Does it make sense to make 0 offers?