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
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
All platforms
RocketMQ version
5.1.2
JDK Version
All versions
Describe the Bug
Fail to start broker in controller mode in 5.1.2
Steps to Reproduce
Start broker in controller mode
What Did You Expect to See?
Start normally
What Did You See Instead?
Fail to start and report NPE
Additional Context
Due to the merging of other pull requests, the initialization order of the replicaManager was adjusted, which caused the automatic master-slave switching mode to malfunction in version 5.1.2.
So do not upgrade to Apache RocketMQ 5.1.2 for broker if you use automatic master-slave switching mode. We will release Apache RocketMQ 5.1.3 ASAP.
The text was updated successfully, but these errors were encountered:
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 platforms
RocketMQ version
5.1.2
JDK Version
All versions
Describe the Bug
Fail to start broker in controller mode in 5.1.2
Steps to Reproduce
Start broker in controller mode
What Did You Expect to See?
Start normally
What Did You See Instead?
Fail to start and report NPE
Additional Context
Due to the merging of other pull requests, the initialization order of the replicaManager was adjusted, which caused the automatic master-slave switching mode to malfunction in version 5.1.2.
So do not upgrade to Apache RocketMQ 5.1.2 for broker if you use automatic master-slave switching mode. We will release Apache RocketMQ 5.1.3 ASAP.
The text was updated successfully, but these errors were encountered: