lizhanhui commented on issue #4807: URL: https://github.com/apache/rocketmq/issues/4807#issuecomment-1211520759
This will make the cluster in an inconsistent state. Publishing of messages would be not load-balanced and subscribers may temporarily ignore some messages on the node that is not present in its route table. Some other undefined behavior may also be possible. This is pretty bad because this breaks the design assumption that brokers connect and report to all name-server nodes. To avoid this from happening, it's advisable to build a monitor tool to compare the routing table of each topic periodically. Once a name server node fails, add an alternative one and isolate it from the cluster. It may also be viable to introduce the consensus algorithm to name server nodes to further improve resilience. -- 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]
