Keep collector workers alive after request cancellation - #2
Merged
Merged
Conversation
RhysSullivan
added this pull request to stack #4
September 24, 2026 17:34
RhysSullivan
marked this pull request as ready for review
September 28, 2026 13:11
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Cancelling one ingest request closed the shared collector worker and returned 503 to other active callers. Keep request cancellation and payload errors local to that request. Ingest and query clients now invalidate the shared worker only for transport failures.
Validation: typecheck and 60 storage tests passed. The stacked integration test reproduces 503 before this change, then verifies successful concurrent writes after cancellation.