Repository navigation
fix(engine): preserve failed reaper batches with delayed retries - #2298
Merged
Merged
Conversation
Hold the first failed ID while healthy removals continue. Stop after a second failure and preserve failed and unprocessed IDs for delayed retry. Keep periodic scheduling alive after rejection and preserve coalesced reaping. Refs: MSG-414
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
A failed interest lookup or removal can abandon a drained completion batch, and an exception escaping the periodic callback can cancel future reaper ticks. This change adds recovery around the serialized/coalesced reaper already in development (MSG-413).
This is the targeted follow-up to MSG-414, not a merge of the older fork implementation in #2286. The existing serialized interest snapshot and coalesced scheduling are retained.
Validation: merged development commit
c16a1786c7463612a50b2c07f9a9a381a683b2c8passed Jenkins #245: 8,824 passed, 0 failed, 38 skipped (8,862 total). ReaperRetryQueueTest: 10 passed; BulkRemoveMessageTaskFailureTest: 7 passed; DestinationReaperInterleavingTest: 15 passed; EventReaperQueueTest: 2 passed; DestinationImplMessageOperationCoverageTest: 24 passed. The existing MSG-413 interleaving cases are retained. Local standalone retry tests andgit diff --checkalso passed; local Maven was dependency-blocked, superseded by the successful development CI run.Refs: MSG-414