RockteMQ-AI commented on issue #227: URL: https://github.com/apache/rocketmq-operator/issues/227#issuecomment-5235132416
**Issue Evaluation** Category: `bug` | Status: **Needs Investigation** Inconsistent Broker data across NameServers is a serious concern for cluster stability. This could indicate: 1. **Replication lag** — NameServers sync route info periodically; if the observation was made during a failover or broker registration, temporary inconsistency is expected (eventual consistency model). 2. **Network partition** — A NameServer may have stale data if it lost contact with the Broker. 3. **Bug in route info management** — If the inconsistency persists, there may be a defect in how NameServers handle broker registration/unregistration. **To help diagnose:** - How long did the inconsistency persist? - Were there any broker restarts or network issues at the time? - Which specific fields were inconsistent (brokerAddr, brokerName, queue mappings)? If the inconsistency is persistent (not transient during failover), this warrants deeper investigation into the NameServer's `RouteInfoManager`. --- *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]
