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

[Bug] Fail to start broker in controller mode in 5.1.2 #6926

Closed
3 tasks done
RongtongJin opened this issue Jun 21, 2023 · 0 comments · Fixed by #6927
Closed
3 tasks done

[Bug] Fail to start broker in controller mode in 5.1.2 #6926

RongtongJin opened this issue Jun 21, 2023 · 0 comments · Fixed by #6927
Labels

Comments

@RongtongJin
Copy link
Contributor

RongtongJin commented Jun 21, 2023

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
image

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
1 participant