LittleBoy18 opened a new issue, #7626: URL: https://github.com/apache/rocketmq/issues/7626
### 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 k8s dledger cluster ### RocketMQ version 5.1.0 ### JDK Version _No response_ ### Describe the Bug Namesrv detects whether the registered node broker id is PrimeSlave. When the registered node is considered to be a prime slave, the perm of all topics will be modified to 4. The candidate node of the ledger cluster joins. Due to network reasons, the broker id registered to namesrv is -1. This will trigger namesrv to modify the perm of all topics to 4. Wait for the master node and candidate node network to return to normal, and then the candidate node will become a follower. node, but the perm of all topics cannot be restored to 6. This part of the logic considers whether it can be optimized. ### Steps to Reproduce 1. Restart the follower node in the dledger cluster When this phenomenon is triggered and the candidate node needs to join the cluster, the master node establishes a connection with the candidate node after a period of time due to network reasons and sends a heartbeat. ### What Did You Expect to See? The candidate node has not received the heartbeat request from the master node, causing the broker id registered to the master node to be -1, which in turn triggers the perm of all topics to 4. It is expected that the perm of all topics will be automatically set to 6 after the normal election is completed. ### What Did You See Instead? After normal election is completed, perm is not set to 6 ### Additional Context _No response_ -- 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
