Quorum queues (recommended) in RabbitMQ - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a quorum queue in RabbitMQ?

A quorum queue is a type of queue in RabbitMQ designed for high availability and data safety. It replicates messages across multiple nodes to prevent data loss if a node fails.

intermediate

How does a quorum queue differ from a classic mirrored queue?

Quorum queues use the Raft consensus algorithm for replication, providing stronger consistency and better fault tolerance than classic mirrored queues, which rely on simpler mirroring.

beginner

What happens if a node in a quorum queue cluster fails?

The quorum queue continues working with the remaining nodes. The Raft algorithm elects a new leader to keep the queue operational without losing messages.

intermediate

How do you declare a quorum queue using RabbitMQ's CLI?

Use the command: rabbitmqctl set_policy ha-quorum-queues "^quorum-" '{"queue-type":"quorum"}' --apply-to queues to apply quorum queue policy to queues starting with 'quorum-'.

beginner

Why are quorum queues recommended over classic mirrored queues?

Because quorum queues provide better data safety, automatic leader election, and improved recovery after failures, making them more reliable for critical messaging.

What algorithm do quorum queues use for replication?

A Simple mirroring

B Raft consensus algorithm

C Two-phase commit

D Paxos algorithm

Quorum queues use the Raft consensus algorithm to replicate messages and maintain consistency across nodes.

Which feature is NOT true about quorum queues?

A They lose messages if a node fails

B They provide automatic leader election

C They replicate messages across multiple nodes

D They are recommended for high availability

Quorum queues are designed to avoid message loss even if a node fails, unlike classic queues without replication.

How do you specify a queue as a quorum queue in RabbitMQ?

A Enable mirroring manually

B Use the 'classic' queue type

C Set the queue-type to 'quorum' in the policy

D Use the 'lazy' queue type

You declare a quorum queue by setting the queue-type to 'quorum' in the queue policy.

What happens when the leader node in a quorum queue cluster fails?

A The queue stops working until manual restart

B The cluster shuts down

C Messages are lost immediately

D A new leader is elected automatically

The Raft algorithm elects a new leader automatically to keep the quorum queue running.

Why might you choose quorum queues over classic mirrored queues?

A Better fault tolerance and data safety

B They use less disk space

C They are simpler to configure

D They do not replicate messages

Quorum queues offer stronger fault tolerance and data safety compared to classic mirrored queues.

Explain what quorum queues are and why they are recommended in RabbitMQ.

Think about how quorum queues keep messages safe and available even if some nodes fail.

Describe how to configure a quorum queue in RabbitMQ and what happens if a node fails.

Focus on the configuration steps and the fault tolerance behavior.

Practice

1. What is the main purpose of a quorum queue in RabbitMQ?

easy

A. To replicate messages across multiple nodes for safety

B. To speed up message delivery by using a single node

C. To store messages only on disk without replication

D. To limit the number of messages in the queue

Solution

1. Step 1: Understand quorum queue purpose

   Quorum queues replicate messages to multiple nodes to ensure safety and durability.

2. Step 2: Compare options

   Only To replicate messages across multiple nodes for safety describes replication for safety, which is the main feature of quorum queues.

3. Final Answer:

   To replicate messages across multiple nodes for safety -> Option A

4. Quick Check:

   Quorum queue purpose = replication for safety [OK]

Hint: Quorum queues replicate messages for safety [OK]

Common Mistakes:

• Thinking quorum queues speed up delivery instead of ensuring safety
• Confusing quorum queues with simple disk storage
• Assuming quorum queues limit message count

2. Which is the correct way to declare a quorum queue in RabbitMQ using the CLI?

easy

A. rabbitmqadmin declare queue name=myqueue durable=true arguments={"x-queue-type":"quorum"}

B. rabbitmqadmin declare queue name=myqueue durable=true

C. rabbitmqctl add_queue myqueue x-queue-type=classic

D. rabbitmqctl add_queue myqueue durable=true

Solution

1. Step 1: Identify quorum queue declaration syntax

   Quorum queues require setting the argument "x-queue-type" to "quorum" when declaring the queue.

2. Step 2: Check options for correct syntax

   Only rabbitmqadmin declare queue name=myqueue durable=true arguments={"x-queue-type":"quorum"} uses the correct syntax with rabbitmqadmin and sets the argument properly.

3. Final Answer:

   rabbitmqadmin declare queue name=myqueue durable=true arguments={"x-queue-type":"quorum"} -> Option A

4. Quick Check:

   Quorum queue declaration = set x-queue-type to quorum [OK]

Hint: Set x-queue-type to quorum in queue arguments [OK]

Common Mistakes:

• Using rabbitmqctl add_queue which is not a valid command
• Not setting x-queue-type argument
• Using classic queue type instead of quorum

3. Given the following command, what will be the type of the queue created?

rabbitmqadmin declare queue name=test durable=true arguments={"x-queue-type":"quorum"}

medium

A. Classic queue

B. Lazy queue

C. Priority queue

D. Quorum queue

Solution

1. Step 1: Analyze the queue declaration command

   The command sets the argument "x-queue-type" to "quorum", which specifies the queue type.

2. Step 2: Determine queue type from argument

   Setting "x-queue-type" to "quorum" creates a quorum queue.

3. Final Answer:

   Quorum queue -> Option D

4. Quick Check:

   Queue type argument = quorum [OK]

Hint: Check x-queue-type argument value for queue type [OK]

Common Mistakes:

• Assuming default classic queue without checking arguments
• Confusing quorum with lazy or priority queues
• Ignoring the arguments field

4. You tried to create a quorum queue but got an error. Which of these is the most likely cause?

medium

A. You declared the queue with a name longer than 10 characters

B. You set durable to false

C. You forgot to set the argument x-queue-type to quorum

D. You used the command rabbitmqctl add_queue

Solution

1. Step 1: Identify required argument for quorum queues

   Quorum queues require the argument "x-queue-type" set to "quorum"; missing this causes errors.

2. Step 2: Evaluate other options

   Durability false is allowed, rabbitmqctl add_queue is invalid command but not the main cause, and queue name length is not restricted to 10 characters.

3. Final Answer:

   You forgot to set the argument x-queue-type to quorum -> Option C

4. Quick Check:

   Missing x-queue-type=quorum causes error [OK]

Hint: Always set x-queue-type=quorum for quorum queues [OK]

Common Mistakes:

• Assuming durability must be true
• Using invalid rabbitmqctl commands
• Believing queue name length causes errors

5. You want to ensure your important messages are never lost even if a RabbitMQ node crashes. Which queue type and setting should you use?

hard

A. Classic queue with durable=false

B. Quorum queue with x-queue-type set to quorum and durable=true

C. Lazy queue with auto-delete=true

D. Classic queue with exclusive=true

Solution

1. Step 1: Identify queue type for message safety

   Quorum queues replicate messages across nodes, protecting against node crashes.

2. Step 2: Check durability setting

   Durable=true ensures messages survive broker restarts, important for message safety.

3. Step 3: Evaluate other options

   Classic queues with durable=false or exclusive=true do not guarantee safety; lazy queues with auto-delete=true remove queues automatically.

4. Final Answer:

   Quorum queue with x-queue-type set to quorum and durable=true -> Option B

5. Quick Check:

   Quorum + durable=true = message safety [OK]

Hint: Use quorum queue with durable=true for safety [OK]

Common Mistakes:

• Using classic queues without durability
• Confusing lazy or exclusive queues with safety features
• Ignoring durable setting