You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Please tell us about your environment:
What is your OS?
What is your client version?
What is your RocketMQ version?
Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):
In java client will update the request node firstly.
But client only updates request node when pullFound in go.
So if the pull request returns PullNoMsgMatched , client will not request master to update offset.
The text was updated successfully, but these errors were encountered:
BUG REPORT
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.
Please tell us about your environment:
What is your OS?
What is your client version?
What is your RocketMQ version?
Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):
![image](https://user-images.githubusercontent.com/46882838/173987492-a9858512-3b6a-463a-8d6e-1f4dcc31a38c.png)
In java client will update the request node firstly.
But client only updates request node when pullFound in go.
![image](https://user-images.githubusercontent.com/46882838/173987730-32e0edfb-af8b-4752-9412-b4e9fe65217a.png)
So if the pull request returns
PullNoMsgMatched
, client will not request master to update offset.The text was updated successfully, but these errors were encountered: