During a network partition in a 5-node RabbitMQ cluster with cluster_partition_handling set to autoheal, what is the expected behavior of queues once the partition heals?
hard📝 Workflow Q8 of 15
RabbitMQ - Clustering
During a network partition in a 5-node RabbitMQ cluster with cluster_partition_handling set to autoheal, what is the expected behavior of queues once the partition heals?
AQueues on the minority partition are deleted and recreated to synchronize with the majority
BQueues on both partitions merge automatically without data loss
CQueues on the minority partition continue independently, causing duplicates
DQueues remain paused indefinitely until manual intervention
Step-by-Step Solution
Solution:
Step 1: Understand autoheal behavior
When autoheal is enabled, RabbitMQ automatically resolves partitions by deleting queues on the minority side.
Step 2: Queue synchronization
Queues on the minority partition are removed and recreated to match the majority partition's state, preventing split-brain inconsistencies.
Final Answer:
Queues on the minority partition are deleted and recreated to synchronize with the majority -> Option A
Quick Check:
Autoheal deletes minority queues to prevent duplicates [OK]
Quick Trick:Autoheal deletes minority queues to sync with majority [OK]
Common Mistakes:
MISTAKES
Assuming queues merge automatically without data loss
