[Bug] Retain highest offset for out-of-order ProcessQueue batches - #11035
Open
zjncs wants to merge 1 commit into
Open
[Bug] Retain highest offset for out-of-order ProcessQueue batches#11035zjncs wants to merge 1 commit into
zjncs wants to merge 1 commit into
Conversation
Signed-off-by: zjncs <18910855655@163.com>
zjncs
marked this pull request as ready for review
September 5, 2026 09:29
RockteMQ-AI
approved these changes
Sep 5, 2026
RockteMQ-AI
left a comment
RockteMQ-AI
left a comment
Contributor
There was a problem hiding this comment.
Summary
Correct fix — when inserting out-of-order messages, queueOffsetMax should retain the highest offset, not just the last one processed. Using Math.max() ensures correctness regardless of insertion order.
The test validates the fix with out-of-order offsets (10, 5) and verifies the returned offset is 11 (max + 1).
LGTM.
Automated review by github-manager-bot
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.
Fixes #10870
ProcessQueue.putMessage now updates queueOffsetMax with Math.max instead of overwriting it for every inserted message. An out-of-order batch can therefore no longer make removeMessage return a stale next offset.
Added a regression test inserting offsets 10 then 5 and asserting the drained next offset is 11.
Verification: git diff --check passed; Maven unavailable locally, CI should run ProcessQueueTest/client checks. AI-assisted contribution.