We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
CentOS
develop
No response
The remoteChannelMap of HeartbeatSyncer was not cleared properly.
Start two proxies in cluster mode, start a consumer and then shut down the consumer.
The remoteChannelMap of HeartbeatSyncer was cleared properly.
The text was updated successfully, but these errors were encountered:
[ISSUE #7429] clean channel map when CLIENT_UNREGISTER in proxy
3808387
Successfully merging a pull request may close this issue.
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
CentOS
RocketMQ version
develop
JDK Version
No response
Describe the Bug
The remoteChannelMap of HeartbeatSyncer was not cleared properly.
Steps to Reproduce
Start two proxies in cluster mode, start a consumer and then shut down the consumer.
What Did You Expect to See?
The remoteChannelMap of HeartbeatSyncer was cleared properly.
What Did You See Instead?
The remoteChannelMap of HeartbeatSyncer was not cleared properly.
Additional Context
No response
The text was updated successfully, but these errors were encountered: