Fair dispatch with prefetch in RabbitMQ - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of 'prefetch' in RabbitMQ?

Prefetch limits the number of unacknowledged messages a consumer can hold. It helps distribute messages fairly among consumers by preventing one from getting overloaded.

beginner

How does fair dispatch improve message processing in RabbitMQ?

Fair dispatch ensures that messages are distributed evenly among consumers based on their ability to process them, avoiding one consumer from receiving too many messages at once.

intermediate

Which RabbitMQ method sets the prefetch count for a consumer?

The method is channel.basicQos(prefetchCount), where prefetchCount is the max number of unacknowledged messages allowed.

beginner

What happens if prefetch is set to 1 in RabbitMQ?

Each consumer receives only one message at a time and must acknowledge it before getting another. This ensures strict fair dispatch.

intermediate

Why is manual message acknowledgment important with fair dispatch?

Manual acknowledgment lets RabbitMQ know when a message is processed. Without it, messages might be lost or unfairly distributed.

What does setting prefetch count to 1 do in RabbitMQ?

A Limits each consumer to one unacknowledged message at a time

B Allows unlimited messages to be sent to consumers

C Disables message acknowledgments

D Sends messages to only one consumer

Setting prefetch to 1 ensures each consumer processes one message at a time before receiving another.

Which method is used to set the prefetch count in RabbitMQ?

A channel.setPrefetch(prefetchCount)

B channel.setQos(prefetchCount)

C channel.prefetchCount(prefetchCount)

D channel.basicQos(prefetchCount)

The correct method is channel.basicQos(prefetchCount) to control message flow.

Why is fair dispatch important in RabbitMQ?

A To evenly distribute messages based on consumer capacity

B To send all messages to the fastest consumer

C To disable message acknowledgments

D To increase message size

Fair dispatch balances load by giving consumers messages they can handle.

What happens if a consumer does not acknowledge a message in RabbitMQ with prefetch set?

A RabbitMQ sends more messages regardless

B RabbitMQ will not send more messages to that consumer until acknowledgment

C The message is deleted immediately

D The consumer is disconnected

RabbitMQ waits for acknowledgment before sending more messages to that consumer.

Which of these is NOT a benefit of using prefetch with fair dispatch?

A Prevents consumer overload

B Ensures even message distribution

C Automatically retries failed messages

D Improves processing efficiency

Prefetch controls message flow but does not handle automatic retries.

Explain how prefetch and manual acknowledgments work together to achieve fair dispatch in RabbitMQ.

Think about how RabbitMQ knows when to send the next message.

Describe the effect of setting prefetch count to 1 on message processing and consumer load.

Imagine a worker who can only handle one task before getting another.

Practice

1. What is the main purpose of setting prefetch_count=1 in RabbitMQ fair dispatch?

easy

A. To ensure each worker receives only one task at a time

B. To allow workers to receive unlimited tasks simultaneously

C. To disable message acknowledgments

D. To increase the queue size automatically

Solution

1. Step 1: Understand prefetch_count meaning

   Prefetch_count controls how many messages a worker can receive before acknowledging previous ones.

2. Step 2: Effect of setting prefetch_count=1

   Setting it to 1 means the worker gets one task at a time, preventing overload and balancing workload.

3. Final Answer:

   To ensure each worker receives only one task at a time -> Option A

4. Quick Check:

   prefetch_count=1 means one task per worker [OK]

Hint: Prefetch 1 means one task per worker at a time [OK]

Common Mistakes:

• Thinking prefetch_count controls queue size
• Believing it disables acknowledgments
• Assuming workers get unlimited tasks

2. Which of the following is the correct way to set prefetch count to 1 using RabbitMQ's channel in Python?

easy

A. channel.set_prefetch(1)

B. channel.qos(prefetch=1)

C. channel.prefetch(1)

D. channel.basic_qos(prefetch_count=1)

Solution

1. Step 1: Recall RabbitMQ Python API method

   The method to set prefetch count is basic_qos with prefetch_count argument.

2. Step 2: Match correct syntax

   Only channel.basic_qos(prefetch_count=1) matches the official API syntax.

3. Final Answer:

   channel.basic_qos(prefetch_count=1) -> Option D

4. Quick Check:

   basic_qos with prefetch_count sets prefetch [OK]

Hint: Use basic_qos(prefetch_count=1) to set prefetch in Python [OK]

Common Mistakes:

• Using incorrect method names like set_prefetch
• Passing wrong argument names
• Confusing prefetch with qos

3. Given the following Python code snippet using RabbitMQ, what will be the output behavior when multiple workers consume from the same queue with prefetch_count=1?

channel.basic_qos(prefetch_count=1)
channel.basic_consume(queue='task_queue', on_message_callback=callback, auto_ack=False)
channel.start_consuming()

medium

A. Messages are processed only by the first worker

B. All workers receive all messages simultaneously

C. Each worker processes one message at a time, distributing tasks evenly

D. Workers process messages without waiting for acknowledgments

Solution

1. Step 1: Understand prefetch_count=1 effect

   With prefetch_count=1, each worker gets one message and must ack before next.

2. Step 2: Effect on multiple workers

   This causes RabbitMQ to distribute messages fairly, so tasks are balanced among workers.

3. Final Answer:

   Each worker processes one message at a time, distributing tasks evenly -> Option C

4. Quick Check:

   prefetch_count=1 balances tasks fairly [OK]

Hint: Prefetch 1 means tasks spread evenly, one per worker [OK]

Common Mistakes:

• Thinking all workers get all messages
• Assuming one worker gets all tasks
• Ignoring manual acknowledgments

4. You set prefetch_count=1 but notice one worker is still overloaded while others are idle. What is the most likely cause?

medium

A. The worker is not sending message acknowledgments properly

B. Prefetch count is set too high

C. The queue is empty

D. Multiple workers have the same consumer tag

Solution

1. Step 1: Analyze prefetch_count=1 behavior

   Prefetch_count=1 limits unacknowledged messages to one per worker.

2. Step 2: Identify cause of overload

   If a worker does not ack messages, RabbitMQ won't send new ones, causing that worker to hold tasks and appear overloaded.

3. Final Answer:

   The worker is not sending message acknowledgments properly -> Option A

4. Quick Check:

   Missing ack blocks new messages [OK]

Hint: Check if worker sends acknowledgments to avoid overload [OK]

Common Mistakes:

• Assuming prefetch count is too high
• Ignoring message acknowledgments
• Confusing consumer tags with load balancing

5. You want to optimize a RabbitMQ system where some workers are slower. How should you configure prefetch to ensure fair dispatch and prevent slow workers from blocking others?

hard

A. Set prefetch_count to a high number to maximize throughput

B. Set prefetch_count=1 so each worker gets one task at a time

C. Disable acknowledgments to speed up processing

D. Use multiple queues instead of prefetch settings

Solution

1. Step 1: Understand slow worker impact

   Slow workers holding many tasks block others if prefetch is high.

2. Step 2: Apply prefetch_count=1 for fair dispatch

   Setting prefetch_count=1 ensures each worker processes one task at a time, preventing blocking.

3. Step 3: Evaluate other options

   High prefetch or disabling acks causes imbalance; multiple queues add complexity.

4. Final Answer:

   Set prefetch_count=1 so each worker gets one task at a time -> Option B

5. Quick Check:

   Prefetch 1 prevents slow worker blocking [OK]

Hint: Use prefetch_count=1 to balance slow and fast workers [OK]

Common Mistakes:

• Setting prefetch too high causing imbalance
• Disabling acknowledgments causing message loss
• Ignoring prefetch and using multiple queues unnecessarily