How to Safely and Reliably (...) While Maintaining 100% Uptime
summary
Claims a rolling upgrade keeps a three‑node RabbitMQ cluster available at all times by stopping one node, installing new binaries, and restarting while two nodes serve traffic; notes 37 RabbitMQ releases in a year and cites concrete commands like rabbitmq upgrade drain to enter maintenance mode, stop_app/start_app and await_startup to block until fully rejoined, plus queue checks for mirror/Quorum safety and optional rebalance. Maintenance mode and careful prechecks prevent alarms, long syncs and resource exhaustion.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:17Upgrade poll results
- 0:45Why you should upgrade
- 2:37Upgrade challenges
- 4:20Pre-upgrade checks
- 5:36Node upgrade steps
- 8:36Finalizing upgrade
- 10:45Automation benefits
- 13:55Q&A Session
related talks
39m101 ways to break your RabbitMQ
30mManaging Quorum Queues at Scale
18mHow to Break RabbitMQ
34mUpdate RabbitMQ now!
22mLessons Learned from Scaling RabbitMQ in a High-Growth (...)
50mOps issues
27mHighly Available Services During Maintenance Events
30mZero Down Time Operations: How to Get Atleast 3 9's of Uptime