GitPopcorn opened a new issue, #7414: URL: https://github.com/apache/rocketmq/issues/7414
### Before Creating the Bug Report - [X] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions). - [X] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/discussions) of this repository and believe that this is not a duplicate. - [X] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ. ### Runtime platform environment Windows 10 21H2 19044,2006 ### RocketMQ version 5.1.3 ### JDK Version 1.8.0_341 ### Describe the Bug After replace the default broker name "broker-a" to "broker-b" in the official quick-start configurations for controller mode, the quick-start demo will not work, and the broker can not be register. ### Steps to Reproduce - Download binary release package `rocketmq-all-5.1.3-bin-release.zip`, unpack it. - Replace the default broker name "broker-a" to "broker-b" in the quick-start configurations for controller mode below: - `rocketmq-all-5.1.3-bin-release\conf\controller\quick-start\broker-n0.conf` - `rocketmq-all-5.1.3-bin-release\conf\controller\quick-start\broker-n1.conf` - Try start RocketMQ in controller mode jsut as document said, with commands below: - `rocketmq-all-5.1.3-bin-release\bin\mqnamesrv -c ..\conf\controller\quick-start\namesrv.conf` - `rocketmq-all-5.1.3-bin-release\bin\mqbroker -n localhost:9876 -c ..\conf\controller\quick-start\broker-n0.conf` - `rocketmq-all-5.1.3-bin-release\bin\mqbroker -n localhost:9876 -c ..\conf\controller\quick-start\broker-n0.conf` - `java -Xms128m -Xmx512m -jar rocketmq-dashboard-1.0.0.jar --server.port=8999 "--rocketmq.config.namesrvAddr=localhost:9876;"` - You will see all the service running well, but the dashboard just can not find correct cluster, and the admin command `rocketmq-all-5.1.3-bin-release\bin\mqadmin getSyncStateSet -a "localhost:9878" -b "broker-b"` won't return right information. - As a contrast, you can replace the broker name back and restart all the service, see how every thing goes right. - Be attention to replace the param `-b "broker-b"` to `-b "broker-a"`. ### What Did You Expect to See? The brokers register and be elected correctly with uniform broker name "broker-b" or "broker-c" or any other valid broker name that is not forbidden. ### What Did You See Instead? It only worked with default broker name "broker-a". ### Additional Context - Is there any document that have mentioned about we can not use any broker name rather than "broker-a" when using a controller mode? - And is there any description in the introduction to tell us could we set multiple master-slave broker group in one controller group? - In fact, I have also test it in my server with a CentOS as operation system, so I'm confirmed that there do be some bug or design in this issue. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
