Memory and disk alarms in RabbitMQ - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to check RabbitMQ memory alarm status.

RabbitMQ

rabbitmqctl status | grep '[1]'

Drag options to blanks, or click blank then click option'

Auptime

Bmemory_alarm

Clisteners

Ddisk_free_limit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'disk_free_limit' instead of 'memory_alarm'.

Searching for 'uptime' which is unrelated.

The memory_alarm keyword shows if the memory alarm is active in RabbitMQ.

2fill in blank

medium

Complete the command to reset the disk alarm on a RabbitMQ node.

RabbitMQ

rabbitmqctl [1] disk_free_alarm

Drag options to blanks, or click blank then click option'

Aset_disk_alarm

Bclear_disk_alarm

Creset_disk_alarm

Dstop_disk_alarm

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'clear_disk_alarm' which is not a valid command.

Using 'set_disk_alarm' which sets, not resets.

The reset_disk_alarm command clears the disk alarm on the node.

3fill in blank

hard

Fix the error in the command to set a memory alarm limit to 2GB.

RabbitMQ

rabbitmqctl set_vm_memory_high_watermark [1]

Drag options to blanks, or click blank then click option'

A0.2

B2g

C2GB

D0.2GB

Attempts:

3 left

💡 Hint

Common Mistakes

Using '2GB' or '2g' which are invalid formats.

Using '0.2GB' which mixes fraction and units.

The memory watermark is set as a fraction of total RAM, so 0.2 means 20% of RAM.

4fill in blank

hard

Fill both blanks to create a command that disables the memory alarm and then checks its status.

RabbitMQ

rabbitmqctl [1] && rabbitmqctl status | grep [2]

Drag options to blanks, or click blank then click option'

Aclear_memory_alarm

Bmemory_alarm

C'memory_alarm'

Dreset_memory_alarm

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'clear_memory_alarm' which is not a valid command.

Not quoting the grep pattern.

Use reset_memory_alarm to disable the alarm, then grep for 'memory_alarm' to check status.

5fill in blank

hard

Fill all three blanks to set a disk free limit to 1GB, verify it, and then reset the disk alarm.

RabbitMQ

rabbitmqctl [1] 1073741824 && rabbitmqctl status | grep [2] && rabbitmqctl [3]

Drag options to blanks, or click blank then click option'

Aset_disk_free_limit

B'disk_free_limit'

Creset_disk_alarm

Dset_vm_memory_high_watermark

Attempts:

3 left

💡 Hint

Common Mistakes

Using memory commands instead of disk commands.

Not quoting the grep pattern.

Using wrong reset command.

Use set_disk_free_limit with bytes for 1GB, grep 'disk_free_limit' to verify, then reset_disk_alarm to clear the alarm.

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