Overview
The company develops one of the world's leading unified physical security platforms. Their RabbitMQ clusters on Windows were experiencing leader election delays causing 6–8 hour downtime incidents.
Challenge
A known RabbitMQ bug was causing leader election delays of 6–8 hours under heavy load, creating significant downtime for security platform operations. The Windows-based deployment added operational complexity, and the client needed to plan a migration to Linux while maintaining stability in a highly controlled deployment environment.
Environment
Windows-based RabbitMQ deployment, client-mandated environment constraints, load-balanced cluster with DNS-based failover.
Approach
AceMQ provided targeted consulting hours for version patching, load balancer configuration, troubleshooting training, and Linux migration planning. The engagement included a repeatable playbook for RabbitMQ restarts and troubleshooting procedures.
Solution
- Identified specific RabbitMQ version patch to resolve leader election bug
- Designed staging environment testing strategy before production rollout
- Configured DNS-based load balancer setup for improved client stability
- Developed repeatable RabbitMQ restart playbook for support staff
- Created troubleshooting training program for internal support teams
- Planned Windows-to-Linux migration path with Kubernetes exploration
Outcome
The client resolved the critical leader election issue, gained internal troubleshooting capabilities, and has a clear migration path from Windows to Linux for improved operational efficiency.