Integration / RabbitMQ Interview Questions
How does RabbitMQ handle network partitions in a cluster?
A network partition splits a cluster into two or more groups of nodes that can no longer see each other, and RabbitMQ's behavior in that scenario depends on the configured cluster_partition_handling strategy.
| Strategy | Behavior |
| ignore (default) | Both sides keep running independently - risks a split-brain with diverging queue state until manually resolved. |
| pause_minority | Nodes that find themselves in a minority partition pause themselves, so only the majority side keeps serving traffic. |
| pause_if_all_down | Pauses a node only if all of a specified set of nodes are unreachable, useful for two-node/witness-style setups. |
| autoheal | Lets both sides run briefly, then automatically picks a 'winning' partition and restarts nodes on the losing side. |
For quorum queues, the underlying Raft protocol adds its own safety net regardless of the cluster-wide setting: only the partition holding a majority of a given queue's replicas can continue committing writes for that queue, so the minority side simply cannot make progress on it until the partition heals.
Which cluster_partition_handling strategy is the RabbitMQ default?
How do quorum queues limit split-brain risk during a partition?
More Related questions...
