This guide explains the two main steps for expanding a RocketMQ cluster—scaling brokers and scaling name servers—detailing when to add resources, configuration changes, and command examples for a smooth horizontal expansion.
The article explains RocketMQ NameServer's lightweight, stateless design, its core routing and metadata management functions, AP‑oriented architecture, fault‑tolerant mechanisms, scalability features, and practical optimization techniques for high availability and low operational cost.
This article explains the role of RocketMQ's NameServer, detailing its registration process, data structures, periodic heartbeat checks, failure cleanup, and how producers and consumers retrieve routing information to send and receive messages efficiently.
The article thoroughly examines RocketMQ’s NameServer, detailing its lightweight registration-center architecture, startup sequence, and the three core routing mechanisms—registration via broker heartbeats, timed removal of stale brokers, and client‑pulled discovery—while explaining key metadata tables and design patterns such as JVM shutdown hooks and read‑write locks for high‑concurrency safety.
This article breaks down the design and source‑code implementation of RocketMQ's NameServer, detailing its core responsibilities, component interactions, and the seven Java classes that together provide network handling, connection management, routing, configuration, and startup logic.
This guide walks you through setting up a fault‑tolerant RocketMQ cluster on two CentOS 7 machines, covering deployment options, environment preparation, Java installation, NameServer and Broker configuration, startup procedures, troubleshooting, and optional console installation.
This article introduces RocketMQ, compares it with ActiveMQ, explains its producer/consumer group model, describes various broker deployment modes, and provides a step‑by‑step dual‑master installation guide with configuration, log, and console setup instructions.
