Queue length limits in RabbitMQ - Step-by-Step Execution

Process Flow - Queue length limits

Start: Queue created

↓

Messages added to queue

↓

Check: Queue length < limit?

No→Reject or Drop message

Yes↓

Message stored in queue

↓

Consumer receives message

↓

Message removed from queue

↓

Repeat as messages arrive

This flow shows how RabbitMQ checks the queue length limit before accepting new messages. If the limit is reached, messages are rejected or dropped.

Execution Sample

RabbitMQ

rabbitmqctl set_policy TTL "^myqueue$" '{"max-length":3, "overflow":"reject-publish"}' --apply-to queues

# Publish 4 messages to 'myqueue'

# Observe queue length and message acceptance

This example sets a max length of 3 messages on 'myqueue' and then tries to add 4 messages, showing how the limit affects message acceptance.

Process Table

Step	Action	Queue Length Before	Message Added?	Queue Length After	Result
1	Add message 1	0	Yes	1	Message accepted
2	Add message 2	1	Yes	2	Message accepted
3	Add message 3	2	Yes	3	Message accepted
4	Add message 4	3	No	3	Message rejected due to max-length limit
5	Consumer receives message	3	N/A	2	Message removed from queue
6	Add message 4 retry	2	Yes	3	Message accepted after space freed

💡 Message 4 initially rejected because queue length reached max-length 3

Status Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	After 6
queue_length	0	1	2	3	3	2	3

Key Moments - 3 Insights

Why was the 4th message rejected at step 4?

Because the queue length was already at the max-length limit of 3, RabbitMQ rejected the new message to prevent overflow, as shown in execution_table row 4.

What happens when a consumer removes a message from the queue?

The queue length decreases by one, freeing space for new messages. This is shown at step 5 where queue_length drops from 3 to 2, allowing message 4 to be accepted later.

Can messages be added again after reaching the max-length limit?

Yes, once the queue length is below the limit (after consumers remove messages), new messages can be accepted again, as seen at step 6.

Visual Quiz - 3 Questions

Look at the execution table, what is the queue length after step 3?

A 3

B 2

C 1

D 0

💡 Hint

Check the 'Queue Length After' column at step 3 in the execution_table.

At which step is the message rejected due to the queue length limit?

A Step 2

B Step 4

C Step 5

D Step 6

💡 Hint

Look for 'Message rejected' in the 'Result' column of the execution_table.

If the max-length was set to 5 instead of 3, what would happen at step 4?

A Message 4 would be rejected

B Queue length would decrease

C Message 4 would be accepted

D Consumer would remove a message

💡 Hint

Refer to the queue length checks in the execution_table and how max-length affects message acceptance.

Concept Snapshot

RabbitMQ queue length limits control how many messages a queue can hold.
Set max-length in queue policy to limit messages.
When limit reached, new messages are rejected or dropped.
Consumers removing messages free space for new ones.
Useful to prevent memory overload and control flow.

Full Transcript

This visual execution trace shows how RabbitMQ enforces queue length limits. When messages are added, RabbitMQ checks if the queue length is below the max-length limit. If yes, the message is accepted and stored. If no, the message is rejected or dropped. When consumers receive messages, the queue length decreases, allowing new messages to be accepted again. The example sets a max-length of 3 on 'myqueue' and tries to add 4 messages. The first three are accepted, the fourth is rejected because the queue is full. After a consumer removes one message, the fourth message is accepted on retry. This helps control queue size and system resources.

Practice

1. What is the main purpose of setting a max-length limit on a RabbitMQ queue?

easy

A. To encrypt messages in the queue

B. To increase the speed of message delivery

C. To limit the number of messages the queue can hold to prevent overload

D. To allow unlimited messages in the queue

Solution

1. Step 1: Understand queue length limits

   Queue length limits control how many messages a queue can hold to avoid memory overload.

2. Step 2: Identify the purpose of max-length

   The max-length setting limits the number of messages to prevent backlog and resource exhaustion.

3. Final Answer:

   To limit the number of messages the queue can hold to prevent overload -> Option C

4. Quick Check:

   Queue length limits = prevent overload [OK]

Hint: Queue length limits prevent too many messages piling up [OK]

Common Mistakes:

• Thinking max-length speeds up delivery
• Confusing max-length with encryption
• Assuming queues can hold unlimited messages

2. Which of the following is the correct syntax to set a queue length limit of 1000 messages using rabbitmqctl?

easy

A. rabbitmqctl set_policy mypolicy "^myqueue$" '{"max-length":1000}' --apply-to queues

B. rabbitmqctl set_policy mypolicy "myqueue" '{max-length=1000}' --apply-to queues

C. rabbitmqctl set_policy mypolicy "^myqueue$" '{max-length:1000}' --apply-to queues

D. rabbitmqctl set_policy mypolicy "^myqueue$" '{"max-length"=1000}' --apply-to queues

Solution

1. Step 1: Review correct JSON syntax for policy

   The policy value must be a JSON string with double quotes around keys and values, e.g., '{"max-length":1000}'.

2. Step 2: Check the full command syntax

   The correct command uses regex pattern with ^ and $ for exact queue name, and --apply-to queues to target queues.

3. Final Answer:

   rabbitmqctl set_policy mypolicy "^myqueue$" '{"max-length":1000}' --apply-to queues -> Option A

4. Quick Check:

   Correct JSON and command syntax = rabbitmqctl set_policy mypolicy "^myqueue$" '{"max-length":1000}' --apply-to queues [OK]

Hint: Use double quotes and JSON format for policy values [OK]

Common Mistakes:

• Using single quotes inside JSON incorrectly
• Missing regex anchors ^ and $
• Using = instead of : in JSON

3. Given the policy set with rabbitmqctl set_policy limit1000 "^task_queue$" '{"max-length":1000}' --apply-to queues, what happens when the queue task_queue receives its 1001st message?

medium

A. The new message is rejected and not added to the queue

B. The oldest message in the queue is dropped to make room for the new one

C. The queue size automatically increases to hold the new message

D. RabbitMQ crashes due to overflow

Solution

1. Step 1: Understand max-length behavior

   When max-length is reached, RabbitMQ drops oldest messages to keep queue size within limit.

2. Step 2: Apply to the 1001st message

   On the 1001st message, the oldest message is removed to add the new one, maintaining max 1000 messages.

3. Final Answer:

   The oldest message in the queue is dropped to make room for the new one -> Option B

4. Quick Check:

   max-length reached = oldest message dropped [OK]

Hint: max-length drops oldest message, never rejects new [OK]

Common Mistakes:

• Thinking new messages get rejected
• Assuming queue size auto-expands
• Believing RabbitMQ crashes on overflow

4. You tried to set a queue length limit with this command: rabbitmqctl set_policy limit "^queue$" '{max-length:500}' --apply-to queues but it did not work. What is the error?

medium

A. The JSON policy value keys and values must be double quoted strings

B. The JSON policy value uses colon instead of equal sign

C. The JSON policy value uses single quotes instead of double quotes

D. The regex pattern is missing anchors ^ and $

Solution

1. Step 1: Check JSON syntax in policy

   JSON requires keys and string values to be double quoted, e.g., '{"max-length":500}'.

2. Step 2: Identify the error in given command

   The command uses '{max-length:500}' without quotes around key, which is invalid JSON.

3. Final Answer:

   The JSON policy value keys and values must be double quoted strings -> Option A

4. Quick Check:

   JSON keys/values need double quotes [OK]

Hint: Always double quote keys and string values in JSON [OK]

Common Mistakes:

• Using single quotes inside JSON
• Using colon instead of colon (correct is colon)
• Ignoring regex anchors (not error here)

5. You want to limit a queue named logs to 500 messages but also want to drop messages older than 1 hour. Which policy configuration correctly applies both limits?

hard

A. rabbitmqctl set_policy loglimit "^logs$" '{"max-length":500, "max-age":60}' --apply-to queues

B. rabbitmqctl set_policy loglimit "^logs$" '{"max-length":500, "max-age":3600}' --apply-to queues

C. rabbitmqctl set_policy loglimit "^logs$" '{"max-length":500, "max-age":60000}' --apply-to queues

D. rabbitmqctl set_policy loglimit "^logs$" '{"max-length":500, "max-age":3600000}' --apply-to queues

Solution

1. Step 1: Understand max-age unit

   RabbitMQ's max-age is in milliseconds, so 1 hour = 3600000 ms.

2. Step 2: Check policy JSON for both limits

   The policy must include both "max-length":500 and "max-age":3600000 correctly formatted.

3. Final Answer:

   rabbitmqctl set_policy loglimit "^logs$" '{"max-length":500, "max-age":3600000}' --apply-to queues -> Option D

4. Quick Check:

   1 hour = 3600000 ms, both limits set [OK]

Hint: Remember max-age is milliseconds, 1 hour = 3600000 [OK]

Common Mistakes:

• Using seconds or minutes instead of milliseconds
• Missing one of the limits in policy
• Incorrect JSON formatting