Repository navigation
Fix orphaned RabbitMQ messages in BackFillerService E2E stress tests - #250
Merged
Merged
Conversation
- Clean up work messages by StressRunId during harness teardown - Preserve foreign messages while scanning shared queues - Bound post-test drain waits - Add tests for owned-message matching and header handling
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
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.
Description
Summary
Fixes orphaned work messages left in shared RabbitMQ queues by BackFillerService E2E stress tests when requests time out without an active consumer.
Changes
StressRunId-scoped cleanup to remove work messages belonging to the current stress run.Verification
Scope
Test-harness changes only. No production monitoring or recovery behaviour is modified.
Known limitations
Foreign messages are temporarily acknowledged while being preserved and subsequently republished. A process failure during this interval could lose a parked message, and concurrent publishers may affect ordering. Cleanup also has a bounded scan limit, so a sufficiently large foreign-message backlog may prevent all owned messages from being reached in one pass.