[Bug] NameServer will be not ready forever when set needWaitForService to true #9182
Closed
3 tasks done
Comments
RongtongJin
pushed a commit
that referenced
this issue
Feb 17, 2025
…aitForService to true (#9183) * Fix NameServer will be not ready forever when set needWaitForService to true * Remove unused import
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
OS: CentOS 6.9
RocketMQ version
branch: (develop|tag 5.1.1) version: 5.1.1
JDK Version
JDK: 1.8.0_202
Describe the Bug
When set needWaitForService of NameServer to true, NameServer will not ready forever.
Steps to Reproduce
Config needWaitForService=true for NameServer
What Did You Expect to See?
NameServer state become ready
What Did You See Instead?
NameServer state become not ready forever
Additional Context
No response
The text was updated successfully, but these errors were encountered: