Ensuring Consistent Restoration of Mirrored Queues with rabbitmq_snapshot

Restoration Strategy & Verification

When a RabbitMQ cluster uses the rabbitmq_snapshot plugin to capture a point‑in‑time state, the goal is to restore that state without losing or duplicating messages, especially for mirrored queues that span multiple nodes.

Key constraints include the necessity of stopping the cluster (or taking each node offline) before restoration to avoid concurrent writes corrupting the replayed state. Restoring only a subset of nodes can leave the cluster in a split‑brain condition, causing inconsistent replication status and potential message loss.

Verification typically relies on comparing pre‑restore and post‑restore queue depths, consumer acknowledgment counts, and message payload checksums. However, the ordering of unacknowledged messages is not guaranteed to be preserved, which can affect deterministic consumers.

Unresolved decision points remain about the optimal restoration sequence for mirrored queues and the most reliable automated verification approach.

Which restoration sequence guarantees that mirrored queues remain consistent across all nodes? How can we programmatically detect duplicate or missing messages after a snapshot restore? What verification metrics should be collected to confirm the ordering of acknowledged versus unacknowledged messages?