caigy commented on issue #131: URL: https://github.com/apache/rocketmq-operator/issues/131#issuecomment-1281746695
@Slideee In current implementation, the complexity will increase as the number of broker clusters increases, because name service controller should update the `namesrvAddr` of EVERY broker properly. Furthermore, if all name servers restart and all of their IPs change, there's no way for broker to register to new name servers. So I think it's worth supporting fetching `namesrvAddr` from `ROCKETMQ_NAMESRV_DOMAIN`. For your design, IMO it's unnecessary to add a new CR, just let name service controller to maintain this service. -- 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]
