Memory and disk alarms in RabbitMQ - Commands & Configuration

Introduction

RabbitMQ needs enough memory and disk space to work well. Memory and disk alarms help stop RabbitMQ from crashing by pausing message handling when resources are low.

When RabbitMQ server memory usage is close to full and you want to prevent crashes.

When disk space on the RabbitMQ server is running low and you want to avoid data loss.

When running RabbitMQ on a shared server and you want to ensure it does not use too many resources.

When you want to monitor RabbitMQ health and get alerts if memory or disk space is too low.

When you want to automatically pause message publishing to avoid overload during resource shortage.

Commands

Check the current status of RabbitMQ including memory and disk alarm states.

Terminal

rabbitmqctl status

Expected Output

Status of node rabbit@my-server ...

[{pid,12345},

 {running_applications,[{rabbit,"RabbitMQ","3.10.7"},

                        {os_mon,"CPO  CXC 138 46"}]},

 {alarms,[memory, disk_free]},

 {memory,[{total,104857600},{connection_readers,1024000}]},

 {disk_free,524288000}]

Set the memory alarm threshold to 40% of total RAM to trigger alarms earlier and protect RabbitMQ.

Terminal

rabbitmqctl set_vm_memory_high_watermark 0.4

Expected Output

No output (command runs silently)

Set the disk free alarm threshold to 500 MB to stop RabbitMQ when disk space is low.

Terminal

rabbitmqctl set_disk_free_limit 500000000

Expected Output

No output (command runs silently)

Clear the memory alarm manually after freeing memory or fixing the issue.

Terminal

rabbitmqctl clear_memory_alarm

Expected Output

No output (command runs silently)

Clear the disk free alarm manually after freeing disk space or fixing the issue.

Terminal

rabbitmqctl clear_disk_free_alarm

Expected Output

No output (command runs silently)

Key Concept

If you remember nothing else from this pattern, remember: RabbitMQ stops accepting messages when memory or disk space is too low to protect itself.

Common Mistakes

Not setting memory or disk alarm thresholds, relying on defaults.

Defaults may be too high or low for your environment, causing unexpected pauses or crashes.

Set memory and disk alarm thresholds based on your server capacity and workload.

Ignoring alarms and not clearing them after fixing resource issues.

RabbitMQ will remain paused and not process messages until alarms are cleared.

Use rabbitmqctl clear_memory_alarm and clear_disk_free_alarm commands after resolving issues.

Setting disk free limit too low, causing RabbitMQ to run out of disk space.

Running out of disk space can cause data loss or RabbitMQ crashes.

Set a safe disk free limit that leaves enough space for RabbitMQ to operate.

Summary

Use rabbitmqctl status to check memory and disk alarm states.

Set memory and disk alarm thresholds with rabbitmqctl set_vm_memory_high_watermark and set_disk_free_limit.

Clear alarms manually with rabbitmqctl clear_memory_alarm and clear_disk_free_alarm after fixing resource issues.

Practice

1. What is the main purpose of memory and disk alarms in RabbitMQ?

easy

A. To increase the speed of message delivery

B. To prevent RabbitMQ from running out of memory or disk space

C. To automatically delete old messages

D. To backup RabbitMQ data to the cloud

Solution

1. Step 1: Understand RabbitMQ resource management

   Memory and disk alarms are designed to monitor resource usage to avoid crashes.

2. Step 2: Identify the role of alarms

   They stop RabbitMQ from accepting more messages when resources are low, protecting stability.

3. Final Answer:

   To prevent RabbitMQ from running out of memory or disk space -> Option B

4. Quick Check:

   Memory and disk alarms protect resources = B [OK]

Hint: Alarms stop resource exhaustion to keep RabbitMQ stable [OK]

Common Mistakes:

• Thinking alarms speed up message delivery
• Confusing alarms with backup features
• Assuming alarms delete messages automatically

2. Which rabbitmqctl command correctly clears a memory alarm?

easy

A. rabbitmqctl clear_memory_alarm --node node@hostname

B. rabbitmqctl clear_memory_alarm node

C. rabbitmqctl clear_memory_alarm --node=node@hostname

D. rabbitmqctl clear_memory_alarm

Solution

1. Step 1: Recall correct syntax for clearing alarms

   The command requires the node name as an argument with the --node flag.

2. Step 2: Compare options

   rabbitmqctl clear_memory_alarm --node node@hostname uses correct syntax.

3. Final Answer:

   rabbitmqctl clear_memory_alarm --node node@hostname -> Option A

4. Quick Check:

   Use --node flag with node name [OK]

Hint: rabbitmqctl clear_memory_alarm --node node@hostname uses correct syntax [OK]

Common Mistakes:

• Using positional argument instead of --node flag
• Using --node=node@hostname syntax
• Using incomplete command without node

3. What will be the output of this command if a disk alarm is active on node rabbit@server1?

rabbitmqctl -n rabbit@server1 list_alarms

medium

A. Error: node not found

B. rabbit@server1 memory

C. []

D. rabbit@server1 disk

Solution

1. Step 1: Understand list_alarms command output

   This command lists active alarms on the specified node in table format.

2. Step 2: Match alarm type with output

   If a disk alarm is active, the output shows rabbit@server1 disk.

3. Final Answer:

   rabbit@server1 disk -> Option D

4. Quick Check:

   Active disk alarm shows rabbit@server1 disk [OK]

Hint: list_alarms shows active alarms in node\talarm table format [OK]

Common Mistakes:

• Confusing memory alarm output with disk alarm
• Expecting empty list when alarm is active
• Assuming command errors if alarm exists

4. You run rabbitmqctl clear_disk_alarm rabbit@server1 but the disk alarm remains active. What is the most likely cause?

medium

A. The disk space is still below the threshold

B. The command syntax is incorrect

C. The node name is misspelled

D. RabbitMQ service is stopped

Solution

1. Step 1: Understand alarm clearing conditions

   Clearing a disk alarm only works if disk space is above the configured threshold.

2. Step 2: Analyze why alarm persists

   If disk space is still low, RabbitMQ keeps the alarm active despite the clear command.

3. Final Answer:

   The disk space is still below the threshold -> Option A

4. Quick Check:

   Alarm clears only if resource condition is met [OK]

Hint: Clear alarms only work if resource usage is back to normal [OK]

Common Mistakes:

• Assuming command syntax error without checking disk space
• Ignoring node name correctness
• Not verifying RabbitMQ service status

5. You want to prevent RabbitMQ from raising a memory alarm until it uses 80% of available RAM instead of the default 40%. Which configuration change achieves this?

hard

A. Run rabbitmqctl set_memory_alarm_threshold 80

B. Set disk_free_limit = 80% in rabbitmq.conf

C. Set vm_memory_high_watermark = 0.8 in rabbitmq.conf

D. Increase system swap space to 80%

Solution

1. Step 1: Identify memory alarm threshold setting

   The vm_memory_high_watermark setting controls memory alarm threshold as a fraction.

2. Step 2: Apply correct value for 80%

   Setting vm_memory_high_watermark = 0.8 means alarm triggers at 80% memory use.

3. Final Answer:

   Set vm_memory_high_watermark = 0.8 in rabbitmq.conf -> Option C

4. Quick Check:

   vm_memory_high_watermark sets memory alarm threshold [OK]

Hint: Use vm_memory_high_watermark to adjust memory alarm threshold [OK]

Common Mistakes:

• Confusing disk_free_limit with memory alarm
• Trying rabbitmqctl command that doesn't exist
• Changing swap space instead of RabbitMQ config