Message TTL (Time To Live) in RabbitMQ - Step-by-Step Execution

Process Flow - Message TTL (Time To Live)

Message Published

↓

Message Enters Queue

↓

TTL Timer Starts

↓

TTL Expires?

No→Message Waits

Yes↓

Message Discarded or Dead-lettered

↓

End

This flow shows how a message with TTL is published, waits in the queue until TTL expires, then is discarded or sent to a dead-letter queue.

Execution Sample

RabbitMQ

rabbitmqctl set_policy TTL "^myqueue$" '{"message-ttl":5000}'
rabbitmqadmin publish routing_key=myqueue payload="Hello"

Set a 5-second TTL on 'myqueue' and publish a message to it.

Process Table

Step	Action	Message State	TTL Timer (ms)	Result
1	Publish message to 'myqueue'	Message in queue	5000	Message accepted
2	Wait 3000 ms	Message in queue	2000	Message still valid
3	Wait 2000 ms	Message in queue	0	TTL expired
4	Remove message from queue	Message removed	N/A	Message discarded or dead-lettered
5	Check queue	Queue empty	N/A	No messages remain

💡 TTL expired at step 3, message removed at step 4, queue empty at step 5

Status Tracker

Variable	Start	After 1	After 2	After 3	After 4	Final
Message State	Not published	In queue	In queue	TTL expired	Removed	Removed
TTL Timer (ms)	N/A	5000	2000	0	N/A	N/A

Key Moments - 2 Insights

Why does the message get removed exactly after 5000 ms?

Because the TTL timer counts down from 5000 ms when the message enters the queue, and at step 3 in the execution_table, TTL reaches 0, triggering removal at step 4.

What happens if the message is consumed before TTL expires?

If consumed earlier, the message is removed normally and TTL no longer matters. This is not shown in the current table but is important to know.

Visual Quiz - 3 Questions

Look at the execution_table, what is the TTL timer value after waiting 3000 ms?

A 3000 ms

B 5000 ms

C 2000 ms

D 0 ms

💡 Hint

Check the TTL Timer column at step 2 in the execution_table.

At which step does the message get removed from the queue?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look at the Result column describing message removal.

If the TTL was set to 10000 ms instead of 5000 ms, what would be the TTL timer at step 3?

A 7000 ms

B 5000 ms

C 8000 ms

D 0 ms

💡 Hint

TTL counts down from initial value minus elapsed time; step 3 is after 5000 ms total wait.

Concept Snapshot

Message TTL in RabbitMQ sets how long a message lives in a queue.
When TTL expires, the message is removed or dead-lettered.
Set TTL via policies or queue arguments.
TTL countdown starts when message enters the queue.
Messages consumed before TTL expire normally.
Useful for expiring stale messages automatically.

Full Transcript

Message TTL (Time To Live) in RabbitMQ controls how long a message stays in a queue before it is discarded or dead-lettered. When a message is published to a queue with a TTL set, a timer starts counting down from the TTL value. If the message is not consumed before the timer reaches zero, the message is removed from the queue. This process helps remove stale messages automatically. The TTL can be set using policies or queue arguments. If a message is consumed before TTL expires, it is removed normally and TTL no longer applies. The visual execution shows the message entering the queue, the TTL timer counting down, and the message removal after TTL expiration.