Clustering connects multiple RabbitMQ nodes into a single logical broker — for scalability and (with replicated queues) high availability. Understanding clustering and its nuances is important for scaling and operating RabbitMQ reliably.
What a cluster is
A RabbitMQ CLUSTER = multiple nodes acting as ONE logical broker:
→ nodes share METADATA (queue/exchange definitions, bindings, users, vhosts) across the cluster
→ clients can connect to any node; load is distributed across nodes
→ scales connection/channel capacity and distributes load
Queues in a cluster (an important nuance)
⚠️ By default, a queue's DATA lives on ONE node (the node where it was declared):
→ other nodes know about the queue (metadata) but route to the owning node
→ if that node FAILS → the queue (and its messages) is UNAVAILABLE
→ so CLUSTERING ALONE does NOT make queues highly available!
→ for HA → use REPLICATED queues (QUORUM QUEUES) that replicate data across nodes
