Bird
0
0

During a rolling upgrade, you notice a node is stuck in 'running_applications' state but not serving messages. What should you do?

hard📝 Workflow Q9 of 15
RabbitMQ - Security and Operations
During a rolling upgrade, you notice a node is stuck in 'running_applications' state but not serving messages. What should you do?
ARestart the RabbitMQ application on that node using <code>rabbitmqctl restart_app</code>
BRemove the node from the cluster permanently
CDelete all queues on that node
DIgnore and continue upgrading other nodes
Step-by-Step Solution
Solution:

  1. Step 1: Restart RabbitMQ application on the stuck node

    Restarting can resolve temporary issues blocking message serving.

  2. Step 2: Verify node resumes normal operation

    Check if node starts serving messages after restart.

  3. Final Answer:

    Restart the RabbitMQ application on that node using rabbitmqctl restart_app -> Option A

  4. Quick Check:

    Fix stuck node by restarting app = C [OK]
Quick Trick: Restart stuck RabbitMQ app to resume message serving [OK]
Common Mistakes:
MISTAKES
  • Removing node unnecessarily
  • Deleting queues without cause
  • Ignoring stuck node

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More RabbitMQ Quizzes
Clustering - Quorum queues (recommended) - Quiz 8hard Clustering - Network partitions and split-brain - Quiz 3easy Clustering - Network partitions and split-brain - Quiz 8hard Clustering - Mirrored queues for redundancy - Quiz 13medium Monitoring and Management - Prometheus and Grafana integration - Quiz 5medium Performance Tuning - Memory and disk alarms - Quiz 5medium Performance Tuning - Batch publishing for throughput - Quiz 7medium Performance Tuning - Batch publishing for throughput - Quiz 1easy Security and Operations - Backup and restore strategies - Quiz 2easy Security and Operations - Authentication backends (LDAP, OAuth) - Quiz 2easy