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

The request offset will not be updated when pull message from slave. #843

Closed
cserwen opened this issue Jun 16, 2022 · 0 comments · Fixed by #844
Closed

The request offset will not be updated when pull message from slave. #843

cserwen opened this issue Jun 16, 2022 · 0 comments · Fixed by #844
Labels
bug Something isn't working

Comments

@cserwen
Copy link
Member

cserwen commented Jun 16, 2022

BUG REPORT

  1. Please describe the issue you observed:

    • What did you do (The steps to reproduce)?
      Client consumes message form slave broker. When commitLog was removed, It will return ResPullRetryImmediately and suggest client pull form master to correct the request offset. But client still pulls from slave and offset is not changed.

    • What did you expect to see?
      The request offset should be min offset of queue.

    • What did you see instead?
      The request offset is not changed.

  2. Please tell us about your environment:

    • What is your OS?

    • What is your client version?

    • What is your RocketMQ version?

  3. Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):
    In java client will update the request node firstly.
    image

But client only updates request node when pullFound in go.
image
So if the pull request returns PullNoMsgMatched , client will not request master to update offset.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant