Handling consumer failures in RabbitMQ - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a consumer failure in RabbitMQ?

A consumer failure happens when a program that reads messages from a queue stops working properly, like crashing or not acknowledging messages.

beginner

Why is message acknowledgment important in handling consumer failures?

Acknowledgment tells RabbitMQ that a message was received and processed. Without it, RabbitMQ can resend the message to avoid losing it if the consumer fails.

intermediate

What happens if a consumer crashes before sending an acknowledgment?

RabbitMQ will requeue the message and deliver it to another consumer to make sure the message is processed.

intermediate

How can you use dead-letter exchanges to handle failed messages?

Dead-letter exchanges receive messages that cannot be processed or are rejected. This helps to isolate and inspect failed messages without losing them.

intermediate

What is the role of prefetch count in consumer failure handling?

Prefetch count limits how many messages a consumer can work on at once. It helps prevent overload and ensures messages are acknowledged before new ones arrive.

What does RabbitMQ do if a consumer fails to acknowledge a message?

A Ignores the message

B Deletes the message permanently

C Requeues the message for another consumer

D Sends an error to the producer

RabbitMQ requeues the message to ensure it is processed by another consumer.

Which feature helps isolate messages that cannot be processed?

A Prefetch count

B Dead-letter exchange

C Message acknowledgment

D Queue mirroring

Dead-letter exchanges collect messages that are rejected or fail processing.

What does setting a prefetch count do?

A Deletes messages after processing

B Creates new queues automatically

C Sends messages to dead-letter exchange

D Limits how many messages a consumer receives before acknowledging

Prefetch count controls the number of unacknowledged messages a consumer can hold.

If a consumer crashes, what happens to the unacknowledged messages?

A They are requeued for other consumers

B They are lost

C They are sent back to the producer

D They are ignored

Unacknowledged messages are requeued to ensure delivery.

Why should consumers acknowledge messages after processing?

A To inform RabbitMQ the message was handled successfully

B To delete the queue

C To create new messages

D To pause the queue

Acknowledgment confirms successful processing and prevents message redelivery.

Explain how RabbitMQ handles messages when a consumer fails before acknowledging them.

Think about what happens to messages that are not confirmed as processed.

Describe the purpose and benefit of using dead-letter exchanges in consumer failure scenarios.

Dead-letter exchanges help manage messages that can't be processed normally.

Practice

1. What is the main purpose of using basic_ack in RabbitMQ consumers?

easy

A. To reject a message and discard it immediately

B. To create a new queue for failed messages

C. To confirm that a message was successfully processed

D. To pause the consumer from receiving more messages

Solution

1. Step 1: Understand message acknowledgment

   In RabbitMQ, basic_ack is used by consumers to tell the server that a message was received and processed successfully.

2. Step 2: Differentiate from rejection

   Unlike basic_nack, which rejects messages, basic_ack confirms success and removes the message from the queue.

3. Final Answer:

   To confirm that a message was successfully processed -> Option C

4. Quick Check:

   basic_ack confirms success [OK]

Hint: basic_ack means message processed OK, not rejected [OK]

Common Mistakes:

• Confusing basic_ack with basic_nack
• Thinking basic_ack rejects messages
• Assuming basic_ack pauses the consumer

2. Which of the following is the correct syntax to reject a message and requeue it in RabbitMQ using the basic_nack method?

easy

A. channel.basic_nack(delivery_tag, requeue=True)

B. channel.basic_nack(delivery_tag, requeue=False)

C. channel.basic_ack(delivery_tag, requeue=True)

D. channel.reject(delivery_tag, requeue=True)

Solution

1. Step 1: Identify correct method and parameters

   The basic_nack method is used to reject a message. To requeue it, the parameter requeue=True must be set.

2. Step 2: Verify syntax correctness

   channel.basic_nack(delivery_tag, requeue=True) correctly calls basic_nack with requeue=True. channel.basic_nack(delivery_tag, requeue=False) rejects without requeue. channel.basic_ack(delivery_tag, requeue=True) uses basic_ack which is for acknowledgment, not rejection. channel.reject(delivery_tag, requeue=True) uses a non-existent method reject.

3. Final Answer:

   channel.basic_nack(delivery_tag, requeue=True) -> Option A

4. Quick Check:

   basic_nack with requeue=True rejects and retries [OK]

Hint: Use basic_nack with requeue=True to retry messages [OK]

Common Mistakes:

• Using basic_ack instead of basic_nack to reject
• Setting requeue=False when retry is needed
• Calling non-existent reject method

3. Given the following code snippet, what will happen if the consumer fails to process the message and calls channel.basic_nack(delivery_tag, requeue=False)?

def callback(ch, method, properties, body):
    try:
        process_message(body)
        ch.basic_ack(method.delivery_tag)
    except Exception:
        ch.basic_nack(method.delivery_tag, requeue=False)

medium

A. The message will be requeued for retry

B. The message will be discarded and not requeued

C. The consumer will crash immediately

D. The message will be acknowledged as successful

Solution

1. Step 1: Analyze basic_nack with requeue=False

   When basic_nack is called with requeue=False, the message is rejected and discarded or sent to a dead-letter queue if configured.

2. Step 2: Understand consumer behavior on failure

   The consumer catches the exception and rejects the message without retrying, so the message won't be requeued.

3. Final Answer:

   The message will be discarded and not requeued -> Option B

4. Quick Check:

   basic_nack with requeue=False discards message [OK]

Hint: requeue=False means no retry, message discarded [OK]

Common Mistakes:

• Assuming message will be retried automatically
• Confusing basic_ack with basic_nack
• Thinking consumer crashes on nack

4. A developer wrote this consumer code but messages are not being requeued on failure. What is the likely error?

def callback(ch, method, properties, body):
    try:
        process_message(body)
        ch.basic_ack(method.delivery_tag)
    except Exception:
        ch.basic_nack(method.delivery_tag)

medium

A. Missing requeue=True in basic_nack call

B. basic_ack should be called before processing

C. Exception block should call basic_ack instead

D. process_message should not be inside try block

Solution

1. Step 1: Check basic_nack parameters

   The basic_nack call lacks the requeue=True parameter, so it defaults to requeue=False, discarding messages instead of retrying.

2. Step 2: Understand correct requeue usage

   To requeue failed messages, basic_nack must be called with requeue=True. Without it, messages are lost or dead-lettered.

3. Final Answer:

   Missing requeue=True in basic_nack call -> Option A

4. Quick Check:

   basic_nack needs requeue=True to retry [OK]

Hint: Always specify requeue=True to retry failed messages [OK]

Common Mistakes:

• Forgetting requeue=True in basic_nack
• Calling basic_ack on failure
• Misplacing try-except blocks

5. You want to ensure failed messages are retried up to 3 times before moving to a dead-letter queue. Which approach best handles this in RabbitMQ consumer code?

hard

A. Set basic_ack to false and let messages stay unacknowledged until retries finish

B. Always call basic_ack and rely on RabbitMQ to retry automatically

C. Use basic_nack with requeue=False and manually resend messages from the consumer

D. Use basic_nack with requeue=True and track retry count in message headers, then reject with requeue=False after 3 tries

Solution

1. Step 1: Understand retry logic with requeue

   To retry failed messages, basic_nack with requeue=True is used. Tracking retry count in message headers helps limit retries.

2. Step 2: Move to dead-letter queue after max retries

   After 3 retries, reject the message with basic_nack and requeue=False to send it to a dead-letter queue for review.

3. Final Answer:

   Use basic_nack with requeue=True and track retry count in message headers, then reject with requeue=False after 3 tries -> Option D

4. Quick Check:

   Retry count + basic_nack controls retries and dead-lettering [OK]

Hint: Track retries in headers; nack with requeue=True until limit [OK]

Common Mistakes:

• Expecting RabbitMQ to retry automatically without tracking
• Using basic_ack to retry messages
• Leaving messages unacknowledged indefinitely