Bird
0
0

You set vm_memory_high_watermark to 0.9 (90%) but RabbitMQ still slows down under load. What is a likely cause?

medium📝 Troubleshoot Q14 of 15
RabbitMQ - Performance Tuning
You set vm_memory_high_watermark to 0.9 (90%) but RabbitMQ still slows down under load. What is a likely cause?
AMessage TTL is set too high.
BThe vm_memory_high_watermark value is too low.
CQueue max-length is set to zero.
DDisk space is full causing slowdowns.
Step-by-Step Solution
Solution:

  1. Step 1: Check memory vs disk usage

    Even if memory limit is high, full disk can cause RabbitMQ to slow due to write delays.

  2. Step 2: Identify common bottleneck

    Disk full or slow disk I/O is a common cause of throughput drops despite memory tuning.

  3. Final Answer:

    Disk space is full causing slowdowns. -> Option D

  4. Quick Check:

    Disk full causes slowdowns = C [OK]
Quick Trick: Check disk space if memory tuning doesn't help [OK]
Common Mistakes:
MISTAKES
  • Assuming memory limit is always the problem
  • Ignoring disk space issues
  • Confusing message TTL with performance

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More RabbitMQ Quizzes
Clustering - RabbitMQ cluster formation - Quiz 7medium Clustering - Mirrored queues for redundancy - Quiz 2easy Clustering - Cluster node types (disc, RAM) - Quiz 5medium Monitoring and Management - Alerting on queue depth and consumer lag - Quiz 4medium Performance Tuning - Consumer prefetch optimization - Quiz 2easy Performance Tuning - Memory and disk alarms - Quiz 10hard Performance Tuning - Flow control mechanism - Quiz 7medium Security and Operations - Shovel and Federation for multi-DC - Quiz 8hard Security and Operations - Why security protects message integrity - Quiz 10hard Security and Operations - Authentication backends (LDAP, OAuth) - Quiz 10hard