-
Notifications
You must be signed in to change notification settings - Fork 11.8k
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] messages will permanently send to other broker when enable sendLatencyFault #7779
Comments
@Tcytw Good catch! Could you submit a pull reqeust to fix the issue? |
@RongtongJin Of course. I have submitted the pull request at #7783 |
It seems that @leizhiyuan had already submitted the same PR, and since he first proposed it, I will merge his PR into trunk. |
…eue permanently Co-authored-by: tianyan <[email protected]>
okay |
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
all OS
RocketMQ version
4.9.x & 5.1.x
JDK Version
JDK1.8
Describe the Bug
After found the topicPublishRouteInfo, producer will select queue.
If enable sendLatencyFault, messageQueue will be replaced by other broker and queueId without recovering.
until producer reboot or broker reboot;
Steps to Reproduce
send message continously with debug on some code for a while.
send message selectOneMessageQueue will set the queue.
then tryToFindTopicPublishInfo will find the queue which is changed
What Did You Expect to See?
the queue changed only at this send message, next send is not influenced
What Did You See Instead?
the queue changed not only at this send message, and queue is changed in the local cache
Additional Context
when set the queueId, I think messagQueue will return with a clone object instead of real message queue in topicRouteInfo
The text was updated successfully, but these errors were encountered: