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

[Bug] pull message result maybe data wrong #6979

Closed
3 tasks done
leizhiyuan opened this issue Jul 1, 2023 · 1 comment · Fixed by #6985
Closed
3 tasks done

[Bug] pull message result maybe data wrong #6979

leizhiyuan opened this issue Jul 1, 2023 · 1 comment · Fixed by #6985

Comments

@leizhiyuan
Copy link
Contributor

leizhiyuan commented Jul 1, 2023

Before Creating the Bug Report

  • I found a bug, not just asking a question, which should be created in GitHub Discussions.

  • I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

  • I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

4.9.7 sdk push consumer + 5.0.0 proxy+5.0.0 broker

RocketMQ version

4.9.7 sdk push consumer + 5.0.0 proxy+5.0.0 broker

JDK Version

1.8

Describe the Bug

client log

2023-06-30 19:43:57,910 WARN RocketmqClient - [BUG] pull message result maybe data wrong, nextBeginOffset: 2947 firstMsgOffset: 9223372036854775807 prevRequestOffset: 2954

proxy log, which I added in org.apache.rocketmq.proxy.remoting.activity.PullMessageActivity

13086:2023-06-30 19:43:57 INFO NettyClientWorkerThread_1 - pull offset monitor,clientHost=10.0.0.3:35702,topic=test,group=x,bname=broker-1-1,queueId=2,queueOffset=2949,commitOffset=2946,maxOffset=2952,nextBeginOffset=2952
13093:2023-06-30 19:43:57 INFO NettyClientWorkerThread_1 - pull offset monitor,clientHost=10.0.0.3:35702,topic=test,group=x,bname=broker-1-1,queueId=2,queueOffset=2954,commitOffset=2954,maxOffset=2947,nextBeginOffset=2947
13095:2023-06-30 19:43:57 INFO NettyClientWorkerThread_2 - pull offset monitor,clientHost=10.0.0.3:35702,topic=test,group=x,bname=broker-1-1,queueId=2,queueOffset=2947,commitOffset=2954,maxOffset=2954,nextBeginOffset=2954

I print responseHeader.getMaxOffset(),just take a look ,the. maxOffset

In a very short period of time, it is not possible for the maxOffset to be smaller than the previous one. The disk is not exceeding the limit, nor is there any penalty for cleaning.

Steps to Reproduce

just run normal case long time

What Did You Expect to See?

no

What Did You See Instead?

maxOffset smaller than before

Additional Context

fix

image

No response

@ferrirW
Copy link
Contributor

ferrirW commented Jul 4, 2023

Wouldn't it be more reasonable to modify the map so that it won't be overwritten?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants