Queue TTL and auto-expiry in RabbitMQ - Commands & Configuration

Introduction

Sometimes messages or queues in RabbitMQ should only live for a limited time. Queue TTL and auto-expiry help automatically remove old messages or unused queues to keep the system clean and efficient.

When you want messages to be discarded if they are not consumed within a certain time.

When you want queues to be deleted automatically if they are unused for a while.

When you want to avoid building up stale messages that waste memory.

When you want to ensure temporary queues do not stay forever after use.

When you want to control resource usage by cleaning up old data automatically.

Config File - queue_ttl_policy.json

queue_ttl_policy.json

{
  "name": "ttl-policy",
  "pattern": "^ttl-queue$",
  "definition": {
    "message-ttl": 60000,
    "expires": 120000
  },
  "priority": 0,
  "apply-to": "queues"
}

This JSON defines a policy named ttl-policy that applies to queues named exactly ttl-queue.

message-ttl sets messages to expire after 60000 milliseconds (1 minute).

expires sets the queue to auto-delete if unused for 120000 milliseconds (2 minutes).

This policy helps remove old messages and delete unused queues automatically.

Commands

This command creates a policy named ttl-policy that sets message TTL to 60000 ms and queue auto-expiry to 120000 ms for queues named ttl-queue.

Terminal

rabbitmqctl set_policy ttl-policy "^ttl-queue$" '{"message-ttl":60000,"expires":120000}' --apply-to queues

Expected Output

Setting policy "ttl-policy" for pattern "^ttl-queue$" to "{\"message-ttl\":60000,\"expires\":120000}" with priority 0 and apply-to queues

→

--apply-to - Specifies that the policy applies to queues

This command creates a queue named ttl-queue that the policy will apply to.

Terminal

rabbitmqadmin declare queue name=ttl-queue durable=false

Expected Output

{

  "queue": "ttl-queue",

  "message_count": 0,

  "consumer_count": 0

}

This command lists queues with their ready and unacknowledged message counts to verify the queue state.

Terminal

rabbitmqctl list_queues name messages_ready messages_unacknowledged

Expected Output

Listing queues ...

name       messages_ready   messages_unacknowledged

ttl-queue  0                0

Key Concept

If you remember nothing else from this pattern, remember: message TTL removes old messages automatically, and queue expires deletes unused queues to keep RabbitMQ clean.

Common Mistakes

Setting message TTL on the queue without applying a policy or creating the queue with TTL arguments.

The TTL settings won't take effect unless applied correctly via policy or queue arguments.

Use rabbitmqctl set_policy with --apply-to queues or declare the queue with TTL arguments.

Confusing message TTL with queue expiry and expecting one to do the other's job.

Message TTL only expires messages, queue expiry deletes the queue if unused; they are separate settings.

Set both message-ttl and expires if you want both behaviors.

Using very short TTL or expiry values in production without testing.

Messages or queues may be deleted too soon, causing lost data or service disruption.

Test TTL and expiry values carefully to balance cleanup and availability.

Summary

Create a policy with message-ttl and expires to control message and queue lifetimes.

Apply the policy to queues matching a name pattern to automate cleanup.

Verify queue creation and message counts to monitor TTL and expiry effects.

Practice

1. What does setting a x-message-ttl on a RabbitMQ queue do?

easy

A. It sets how long messages stay in the queue before they expire.

B. It deletes the queue after a certain time of inactivity.

C. It limits the number of messages the queue can hold.

D. It changes the priority of messages in the queue.

Solution

1. Step 1: Understand x-message-ttl meaning

   The x-message-ttl setting controls the time-to-live for messages in the queue, meaning how long each message can stay before expiring.

2. Step 2: Differentiate from queue auto-expiry

   Queue auto-expiry deletes the entire queue after inactivity, which is different from message TTL.

3. Final Answer:

   It sets how long messages stay in the queue before they expire. -> Option A

4. Quick Check:

   Message TTL = message lifetime [OK]

Hint: Message TTL controls message lifetime, not queue deletion [OK]

Common Mistakes:

• Confusing message TTL with queue auto-expiry
• Thinking TTL limits message count
• Assuming TTL changes message priority

2. Which of the following is the correct way to set a queue TTL of 60000 milliseconds in RabbitMQ using arguments?

easy

A. {"x-message-ttl":60000}

B. {"x-expires":60000}

C. {"x-max-length":60000}

D. {"x-priority":60000}

Solution

1. Step 1: Identify the correct argument for message TTL

   The argument x-message-ttl is used to set the time-to-live for messages in milliseconds.

2. Step 2: Verify other options

   x-expires is for queue auto-expiry, x-max-length limits queue size, and x-priority sets message priority, so they are incorrect here.

3. Final Answer:

   {"x-message-ttl":60000} -> Option A

4. Quick Check:

   TTL argument = x-message-ttl [OK]

Hint: Use x-message-ttl for message expiry time in ms [OK]

Common Mistakes:

• Using x-expires instead of x-message-ttl
• Confusing max-length with TTL
• Setting priority instead of TTL

3. Given a queue with x-message-ttl set to 30000 ms and a message published at time 0, what happens if the message is not consumed by 35000 ms?

medium

A. The queue is deleted after 30000 ms.

B. The message is removed from the queue automatically after 30000 ms.

C. The message stays in the queue indefinitely until consumed.

D. The message priority is increased after 30000 ms.

Solution

1. Step 1: Understand message TTL effect

   Message TTL of 30000 ms means messages expire and are removed if not consumed within 30 seconds.

2. Step 2: Apply timing to message

   Since the message is not consumed by 35000 ms (which is after 30000 ms), it will be removed automatically.

3. Final Answer:

   The message is removed from the queue automatically after 30000 ms. -> Option B

4. Quick Check:

   Message expires after TTL [OK]

Hint: Messages expire after TTL if not consumed [OK]

Common Mistakes:

• Thinking messages stay forever without consumption
• Confusing message TTL with queue deletion
• Assuming priority changes with TTL

4. You set x-expires to 60000 on a queue, but the queue is not deleted after 1 minute of inactivity. What could be the reason?

medium

A. The x-expires value must be set in seconds, not milliseconds.

B. RabbitMQ does not support queue auto-expiry.

C. The queue TTL must be set for the queue to expire.

D. The queue has active consumers or unacknowledged messages.

Solution

1. Step 1: Understand x-expires behavior

   x-expires deletes the queue after the specified time of inactivity, meaning no consumers and no unacknowledged messages.

2. Step 2: Identify why queue is not deleted

   If the queue has active consumers or unacknowledged messages, it is considered active and will not be deleted despite x-expires.

3. Final Answer:

   The queue has active consumers or unacknowledged messages. -> Option D

4. Quick Check:

   Queue expires only if inactive [OK]

Hint: Queue expires only when fully inactive (no consumers) [OK]

Common Mistakes:

• Confusing milliseconds with seconds for x-expires
• Thinking message TTL controls queue expiry
• Believing RabbitMQ lacks auto-expiry feature

5. You want a queue to automatically delete itself if unused for 2 minutes and also want messages to expire after 1 minute. Which configuration is correct?

hard

A. {"x-max-length":120000, "x-expires":60000}

B. {"x-message-ttl":120000, "x-expires":60000}

C. {"x-expires":120000, "x-message-ttl":60000}

D. {"x-expires":60000, "x-message-ttl":120000}

Solution

1. Step 1: Match time values to correct arguments

   x-expires controls queue auto-expiry after inactivity, so 2 minutes = 120000 ms should be set here. x-message-ttl controls message expiry, so 1 minute = 60000 ms goes here.

2. Step 2: Verify option correctness

   {"x-expires":120000, "x-message-ttl":60000} correctly assigns x-expires to 120000 and x-message-ttl to 60000. Other options swap or misuse these values.

3. Final Answer:

   {"x-expires":120000, "x-message-ttl":60000} -> Option C

4. Quick Check:

   Queue expiry = 120000 ms, Message TTL = 60000 ms [OK]

Hint: Set x-expires for queue, x-message-ttl for messages [OK]

Common Mistakes:

• Swapping TTL and expires values
• Using max-length instead of TTL or expires
• Confusing milliseconds with seconds