Work queue for task distribution in RabbitMQ - Commands & Configuration

Introduction

When you have many tasks to do and want to share them fairly among workers, a work queue helps by holding tasks until workers are ready. This way, no worker is overloaded and tasks get done smoothly.

When you want to split a big job into smaller tasks and have multiple workers process them.

When you need to make sure tasks are not lost if a worker crashes.

When you want to balance the load so no single worker is overwhelmed.

When tasks come in faster than workers can handle and need to wait in line.

When you want to add or remove workers without stopping the system.

Config File - work_queue_producer.py

work_queue_producer.py

import pika

connection = pika.BlockingConnection(pika.ConnectionParameters('localhost'))
channel = connection.channel()

channel.queue_declare(queue='task_queue', durable=True)

message = ' '.join(['Hello'] * 5)
channel.basic_publish(
    exchange='',
    routing_key='task_queue',
    body=message,
    properties=pika.BasicProperties(
        delivery_mode=2  # make message persistent
    ))
print(" [x] Sent %r" % message)
connection.close()

This Python script connects to RabbitMQ on localhost and declares a durable queue named task_queue. It sends a persistent message to this queue. Durable queues and persistent messages ensure tasks are not lost if RabbitMQ restarts.

Commands

Run the producer script to send a task message to the work queue.

Terminal

python work_queue_producer.py

Expected Output

 [x] Sent 'Hello Hello Hello Hello Hello'

Check the list of queues on RabbitMQ server to confirm the queue exists and see message counts.

Terminal

rabbitmqctl list_queues

Expected Output

Listing queues ...

task_queue	1

...done.

Run the consumer script to receive and process tasks from the work queue.

Terminal

python work_queue_consumer.py

Expected Output

 [*] Waiting for messages. To exit press CTRL+C

 [x] Received Hello Hello Hello Hello Hello

 [x] Done

Key Concept

If you remember nothing else, remember: durable queues and persistent messages keep tasks safe and fairly distributed among workers.

Common Mistakes

Not declaring the queue as durable in both producer and consumer.

If the queue is not durable, tasks will be lost if RabbitMQ restarts.

Always declare the queue with durable=True in both producer and consumer scripts.

Not setting message delivery_mode to 2 (persistent) when publishing.

Messages will not be saved to disk and can be lost on server failure.

Set delivery_mode=2 in message properties to make messages persistent.

Not acknowledging messages in the consumer.

RabbitMQ will not know when a task is done and may resend or lose track of tasks.

Use manual message acknowledgments in the consumer to confirm task completion.

Summary

Declare a durable queue to hold tasks safely.

Send persistent messages so tasks survive server restarts.

Run consumers that receive tasks and acknowledge them after processing.

Practice

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

easy

A. To create a backup of messages

B. To distribute tasks among multiple workers safely

C. To store user login information

D. To encrypt messages for security

Solution

1. Step 1: Understand the role of work queues

   Work queues are designed to share tasks among many workers so that the workload is balanced and tasks are processed efficiently.

2. Step 2: Eliminate unrelated options

   Storing login info, backing up messages, or encrypting messages are not the primary functions of work queues.

3. Final Answer:

   To distribute tasks among multiple workers safely -> Option B

4. Quick Check:

   Work queue = task distribution [OK]

Hint: Work queues share tasks among workers, not store or encrypt data [OK]

Common Mistakes:

• Confusing work queues with message encryption
• Thinking work queues store user data
• Assuming work queues backup messages automatically

2. Which RabbitMQ queue declaration option makes the queue survive server restarts?

easy

A. durable: true

B. autoDelete: true

C. exclusive: true

D. passive: true

Solution

1. Step 1: Identify durability option

   The 'durable: true' option ensures the queue is saved to disk and survives RabbitMQ server restarts.

2. Step 2: Understand other options

   'autoDelete' removes the queue when no consumers remain, 'exclusive' restricts queue to one connection, and 'passive' checks for queue existence without creating it.

3. Final Answer:

   durable: true -> Option A

4. Quick Check:

   durable = survive restart [OK]

Hint: Durable queues survive restarts; autoDelete removes queues [OK]

Common Mistakes:

• Using autoDelete instead of durable for persistence
• Confusing exclusive with durability
• Thinking passive creates durable queues

3. Given this worker code snippet in Python using pika:

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

What happens if the worker crashes before sending an acknowledgment?

medium

A. The message is requeued and delivered to another worker

B. The queue deletes all messages

C. The message is acknowledged automatically

D. The message is lost and never processed again

Solution

1. Step 1: Understand auto_ack=False behavior

   With auto_ack set to False, the worker must explicitly acknowledge messages after processing.

2. Step 2: Effect of worker crash before ack

   If the worker crashes before ack, RabbitMQ requeues the message to deliver it to another worker, ensuring no task is lost.

3. Final Answer:

   The message is requeued and delivered to another worker -> Option A

4. Quick Check:

   auto_ack=False + crash = requeue message [OK]

Hint: auto_ack=False means unacked messages get requeued on crash [OK]

Common Mistakes:

• Assuming messages are lost without ack
• Thinking messages auto-acknowledge on delivery
• Believing queue deletes messages on worker failure

4. You wrote this code to declare a durable queue:

channel.queue_declare(queue='task_queue', durable=False)

Why might this cause task loss after RabbitMQ restarts?

medium

A. Because exclusive=True is missing

B. Because the queue name is invalid

C. Because durable=True deletes messages on restart

D. Because durable=False means the queue is deleted on restart

Solution

1. Step 1: Analyze durable flag effect

   Setting durable=False means the queue is temporary and will be deleted when RabbitMQ restarts.

2. Step 2: Consequence on task persistence

   Since the queue is deleted, any unprocessed tasks in it are lost after restart.

3. Final Answer:

   Because durable=False means the queue is deleted on restart -> Option D

4. Quick Check:

   durable=False = queue lost on restart [OK]

Hint: durable=False queues vanish on restart, losing tasks [OK]

Common Mistakes:

• Confusing durable with exclusive
• Thinking queue name causes loss
• Believing durable=True deletes messages

5. You want to ensure tasks are not lost even if RabbitMQ crashes and workers fail. Which combination of settings should you use for the queue and messages?

hard

A. Declare queue with autoDelete=true and publish messages with delivery_mode=1

B. Declare queue with exclusive=true and publish messages with delivery_mode=1

C. Declare queue with durable=true and publish messages with delivery_mode=2

D. Declare queue with durable=false and publish messages with delivery_mode=2

Solution

1. Step 1: Ensure queue durability

   Setting durable=true makes the queue survive RabbitMQ restarts, preventing loss of the queue itself.

2. Step 2: Make messages persistent

   Publishing messages with delivery_mode=2 marks them as persistent, so they are saved to disk and not lost on server crash.

3. Step 3: Understand why other options fail

   autoDelete=true deletes the queue when no consumers remain, exclusive=true restricts queue to one connection, and durable=false means queue is temporary. delivery_mode=1 means messages are transient and can be lost.

4. Final Answer:

   Declare queue with durable=true and publish messages with delivery_mode=2 -> Option C

5. Quick Check:

   durable queue + persistent messages = no loss [OK]

Hint: Durable queue + delivery_mode=2 messages prevent loss [OK]

Common Mistakes:

• Using autoDelete instead of durable for persistence
• Publishing messages without delivery_mode=2
• Confusing exclusive with durability