RockteMQ-AI commented on issue #227: URL: https://github.com/apache/rocketmq-operator/issues/227#issuecomment-5395026963
**Issue Evaluation** Category: `bug` | Status: **Needs Info** Inconsistent broker registration data across NameServers is a serious issue that can affect routing and client connections. However, more information is needed to diagnose: 1. **Cluster topology:** How many NameServers and Brokers are deployed? Are all NameServers in the same cluster? 2. **Reproducibility:** Is the inconsistency persistent, or does it resolve after some time? 3. **Network:** Are there any network partitions or latency issues between NameServers and Brokers? 4. **Operator version:** Which version of the operator and RocketMQ are you using? Broker registration to NameServers is push-based (Brokers periodically register with all configured NameServers). Inconsistency suggests either: - A Broker is not configured with all NameServer addresses - Network issues preventing registration to some NameServers - A timing issue during Broker startup/failover Please provide the above details for further investigation. --- *Automated evaluation by github-manager* -- 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]
