Welcome everyone to pay attention to my WeChat public account [ Lao Zhouchao Architecture ], the principle of Java back-end mainstream technology stack, source code analysis, architecture, and various Internet solutions with high concurrency, high performance, and high availability.
I. Introduction
In the first three articles we introduced
My architectural dream: (Ninety-seven) RocketMQ high-availability mechanism of message middleware-high availability of message storage
My architectural dream: (Ninety-eight) RocketMQ high-availability mechanism of message middleware-high availability of message sending
My architectural dream: (Ninety-nine) RocketMQ's high availability mechanism of message middleware-high availability of message consumption
In this article, let’s talk about how cluster management guarantees high availability. It is not only the last article about RocketMQ's high availability mechanism, but also the 100th article in the "My Architecture Dream" column. Hundreds, thank you everyone for walking along with Lao Zhou's article, thank you.
The high availability of cluster management is mainly reflected in the design of NameServer, which assumes the role of routing registry. When part of the NameServer nodes go down, there will be no bad effects. Only one NameServer node RocketMQ cluster can operate normally. Even if the NameServer is all down, it will not affect the Broker, Producer and Consumer that are already running.
Before talking about NameServer, do we have the following thoughts