Bird
0
0

A node joined a cluster but queues are missing after restart. What is a likely cause?

medium📝 Troubleshoot Q7 of 15
RabbitMQ - Clustering
A node joined a cluster but queues are missing after restart. What is a likely cause?
ACluster was formed with mismatched RabbitMQ versions
BNode was joined as a RAM node instead of disk node
CNetwork firewall blocked cluster communication
DNode hostname was incorrectly set
Step-by-Step Solution
Solution:

  1. Step 1: Identify queue persistence behavior

    RAM nodes do not persist queues to disk, so queues disappear after restart.

  2. Step 2: Match cause to symptom

    Missing queues after restart indicate node is RAM type, not disk type.

  3. Final Answer:

    Node was joined as a RAM node instead of disk node -> Option B

  4. Quick Check:

    Missing queues after restart = RAM node issue [OK]
Quick Trick: Disk nodes keep queues; RAM nodes lose them on restart [OK]
Common Mistakes:
MISTAKES
  • Blaming version mismatch for missing queues
  • Assuming firewall causes queue loss
  • Thinking hostname affects queue persistence

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More RabbitMQ Quizzes
Clustering - Cluster node types (disc, RAM) - Quiz 5medium Clustering - Cluster node types (disc, RAM) - Quiz 8hard Monitoring and Management - Why monitoring prevents production incidents - Quiz 5medium Monitoring and Management - Log analysis and troubleshooting - Quiz 7medium Monitoring and Management - Alerting on queue depth and consumer lag - Quiz 4medium Performance Tuning - Flow control mechanism - Quiz 15hard Security and Operations - Backup and restore strategies - Quiz 3easy Security and Operations - Authentication backends (LDAP, OAuth) - Quiz 15hard Security and Operations - Shovel and Federation for multi-DC - Quiz 13medium Security and Operations - Upgrade procedures - Quiz 7medium