RockteMQ-AI commented on issue #227: URL: https://github.com/apache/rocketmq-operator/issues/227#issuecomment-5364749196
**Issue Evaluation** Category: `bug` | Status: **Needs Investigation** This reports inconsistent broker data retrieval when querying different NameServer nodes. In a correctly functioning cluster, all NameServer instances should return the same broker list since they receive heartbeat registrations from all brokers. **Possible causes:** 1. Network partition between some brokers and one NameServer instance 2. Stale route data due to heartbeat timeout misconfiguration 3. NameServer not properly syncing route info (though NameServers are independent — they don't sync with each other) **Key point:** NameServers in RocketMQ do NOT replicate data between each other. Each broker registers with ALL NameServers independently. If one NameServer shows different data, it means some brokers are not successfully registering with that specific NameServer. Please verify: - All brokers have all NameServer addresses in their configuration - Network connectivity from each broker to each NameServer - NameServer heartbeat timeout settings (`scanNotActiveBrokerInterval`) --- *Automated evaluation by RockteMQ-AI* -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
