RockteMQ-AI commented on issue #52: URL: https://github.com/apache/rocketmq-operator/issues/52#issuecomment-5223760491
**Issue Evaluation** Category: `enhancement` | Status: **Evaluated** **Feasibility:** feasible (requires coordinated changes in Broker + Operator) **Scope:** Broker NameServer address refresh, Operator scaling logic **Compatibility:** backward-compatible if Broker gracefully handles new NameServer registration The analysis is correct: Broker currently loads NameServer addresses at startup and does not dynamically refresh them. When the Operator scales up the NameServer cluster, it must restart Brokers to pick up the new addresses. This is a valid enhancement request. A proper fix would involve: 1. Broker supporting dynamic NameServer list refresh (e.g., via AdminTools API or file watch) 2. Operator leveraging that mechanism instead of rolling restarts Marking as a long-term enhancement. Implementation requires cross-module coordination. --- *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]
