Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ISSUE #6570] Fix the issue that expectLogicOffset is greater than currentLogicOffset in consumeQueue build when the message is illegal #6641

Merged
merged 7 commits into from
Apr 26, 2023

Conversation

RongtongJin
Copy link
Contributor

Make sure set the target branch to develop

What is the purpose of the change

fix #6570

Brief changelog

Fix the issue that expectLogicOffset is greater than currentLogicOffset in consumeQueue build

Verifying this change

XXXX

Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

  • Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
  • Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
  • Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test to make sure integration-test pass.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

@codecov-commenter
Copy link

Codecov Report

Merging #6641 (4ed3faf) into develop (14ad16b) will decrease coverage by 0.04%.
The diff coverage is 77.46%.

@@              Coverage Diff              @@
##             develop    #6641      +/-   ##
=============================================
- Coverage      43.13%   43.10%   -0.04%     
+ Complexity      9005     8994      -11     
=============================================
  Files           1107     1107              
  Lines          78297    78332      +35     
  Branches       10204    10212       +8     
=============================================
- Hits           33776    33765      -11     
- Misses         40302    40329      +27     
- Partials        4219     4238      +19     
Impacted Files Coverage Δ
...n/java/org/apache/rocketmq/store/MessageStore.java 0.00% <ø> (ø)
...ketmq/store/plugin/AbstractPluginMessageStore.java 0.00% <0.00%> (ø)
...main/java/org/apache/rocketmq/store/CommitLog.java 64.97% <66.66%> (-0.27%) ⬇️
...apache/rocketmq/store/queue/BatchConsumeQueue.java 70.37% <75.00%> (+0.16%) ⬆️
...n/java/org/apache/rocketmq/store/ConsumeQueue.java 66.29% <76.19%> (+0.06%) ⬆️
...org/apache/rocketmq/store/DefaultMessageStore.java 46.80% <80.00%> (-0.06%) ⬇️
...apache/rocketmq/store/queue/ConsumeQueueStore.java 47.63% <83.33%> (+0.57%) ⬆️
...ache/rocketmq/store/queue/QueueOffsetOperator.java 80.48% <91.66%> (ø)
...pache/rocketmq/store/dledger/DLedgerCommitLog.java 76.90% <100.00%> (+0.09%) ⬆️

... and 22 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

guyinyou
guyinyou previously approved these changes Apr 24, 2023
GenerousMan
GenerousMan previously approved these changes Apr 24, 2023
@RongtongJin RongtongJin dismissed stale reviews from GenerousMan and guyinyou via f717dfc April 25, 2023 07:35
Copy link
Contributor

@fuyou001 fuyou001 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Long queueOffset = ConcurrentHashMapUtils.computeIfAbsent(this.topicQueueTable, topicQueueKey, k -> 0L);
this.topicQueueTable.put(topicQueueKey, queueOffset + messageNum);
return queueOffset;
topicQueueTable.put(topicQueueKey, queueOffset + messageNum);
}

public void updateQueueOffset(String topicQueueKey, long offset) {
this.topicQueueTable.put(topicQueueKey, offset);
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updateQueueOffset seems not be used.

@odbozhou odbozhou merged commit e3b8178 into apache:develop Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

expectLogicOffset is greater than currentLogicOffset in consumeQueue build when the message is illegal
10 participants