Memory and disk alarms in RabbitMQ - Cheat Sheet & Quick Revision

Recall & Review

beginner

What triggers a memory alarm in RabbitMQ?

A memory alarm is triggered when RabbitMQ's used memory exceeds the configured memory high watermark, which is a limit set to prevent the server from running out of memory.

beginner

What happens when a disk alarm is raised in RabbitMQ?

When a disk alarm is raised, RabbitMQ stops accepting new messages to prevent running out of disk space, ensuring stability and data integrity.

intermediate

How can you check the current memory alarm status in RabbitMQ?

You can check the memory alarm status using the command: rabbitmqctl status or by inspecting the management UI under the node's overview section.

intermediate

Which configuration setting controls the memory high watermark in RabbitMQ?

The memory high watermark is controlled by the setting 'vm_memory_high_watermark' in the RabbitMQ configuration file or environment variables.

beginner

Why is it important to monitor disk space and memory usage in RabbitMQ?

Monitoring disk space and memory usage prevents RabbitMQ from crashing or losing messages by triggering alarms that stop message flow before resources are exhausted.

What does RabbitMQ do when the memory alarm is triggered?

A Restarts the server

B Deletes old messages automatically

C Stops accepting new messages

D Sends an email alert only

When memory alarm triggers, RabbitMQ stops accepting new messages to avoid running out of memory.

Which command helps check RabbitMQ's memory and disk alarm status?

A rabbitmqctl status

B rabbitmqctl list_queues

C rabbitmqctl reset

D rabbitmqctl start_app

The 'rabbitmqctl status' command shows node status including memory and disk alarms.

What is the default action when a disk alarm is raised in RabbitMQ?

A Increase disk space automatically

B Stop accepting new messages

C Delete oldest messages

D Send a warning but continue processing

RabbitMQ stops accepting new messages to prevent disk space exhaustion.

Which configuration parameter sets the memory limit for RabbitMQ alarms?

A heartbeat_interval

B disk_free_limit

C max_connections

D vm_memory_high_watermark

'vm_memory_high_watermark' controls the memory usage limit triggering alarms.

Why should RabbitMQ administrators monitor memory and disk alarms?

A To prevent server crashes and message loss

B To improve message delivery speed

C To reduce network traffic

D To automatically backup messages

Monitoring alarms helps avoid crashes and message loss by managing resource limits.

Explain how RabbitMQ handles memory and disk alarms and why they are important.

Think about what happens when resources run low and how RabbitMQ protects itself.

Describe how to check and configure memory and disk alarms in RabbitMQ.

Consider commands and config settings involved.

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