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 #9025] [RIP-73] Fix reset offset not effective in Pop Consumption #9087

Merged
merged 1 commit into from
Dec 30, 2024

Conversation

lizhimins
Copy link
Member

Which Issue(s) This PR Fixes

Fixes #9025

Brief Description

How Did You Test This Change?

@lizhimins lizhimins changed the title [ISSUE #9025] [RIP-73] Fix Pop Consumption reset offset [ISSUE #9025] [RIP-73] Fix reset offset not effective in Pop Consumption Dec 30, 2024
@codecov-commenter
Copy link

Codecov Report

Attention: Patch coverage is 20.00000% with 4 lines in your changes missing coverage. Please review.

Project coverage is 48.00%. Comparing base (19393e0) to head (95e2886).
Report is 1 commits behind head on develop.

Files with missing lines Patch % Lines
...ocketmq/broker/processor/AdminBrokerProcessor.java 20.00% 3 Missing and 1 partial ⚠️
Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #9087      +/-   ##
=============================================
+ Coverage      47.97%   48.00%   +0.02%     
- Complexity     12045    12050       +5     
=============================================
  Files           1320     1320              
  Lines          92779    92782       +3     
  Branches       11896    11897       +1     
=============================================
+ Hits           44511    44537      +26     
+ Misses         42756    42741      -15     
+ Partials        5512     5504       -8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

if (brokerController.getBrokerConfig().isPopConsumerKVServiceEnable()) {
brokerController.getPopConsumerService().clearCache(group, topic, queueId);
brokerController.getPopConsumerService().clearCache(group, topic, entry.getKey());
brokerController.getConsumerOffsetManager().commitPullOffset(
Copy link
Contributor

Choose a reason for hiding this comment

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

Notice: here if we use the same consumer group to do pull and pop at the same time, they both commit the pull offset, May be pop requests may miss some messages here.

Copy link
Contributor

@lollipopjin lollipopjin left a comment

Choose a reason for hiding this comment

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

LGTM

@lizhimins lizhimins merged commit f32fe78 into apache:develop Dec 30, 2024
10 of 11 checks passed
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.

[Feature] [RIP‐73] Pop Consumption Improvement Based on RocksDB
3 participants