I did test the cluster. I caused a check to trigger, then shutdown the primary RabbitMQ server. I made sure the clients connected to the other RabibtMQ server, then caused the correct the issue on the check. I saw that the check was sending the OK status, however the dashboard would never clear the check. Once I mirrored the queues everything worked.
I did make a lot of changes yesterday, adding a password to redis, binding redis on an external IP, setting up a second sensu server, and then clustering RabbitMQ. Today I have un done all that and am going to test each piece to determine if I need to mirror the queues or not. Everything is running as VM’s using vagrant on my local laptop so it is pretty easy to re-configure everything.
On Tuesday, June 25, 2013 10:56:27 AM UTC-4, Quenten Griffith wrote:
I am looking into the various options of setting up Sensu with 2 servers for redundancy. From searching the groups it appears it may be recommend to use RabbitMQ federation. One thing that I am missing the understanding on, is if one RabbitMQ server goes down, do you have to change all the agents to point to the other RabbitMQ server manually? Has anyone used Sensu with a clustered pair of RabbitMQ servers using a load balancer? That way it would avoid having to change a bunch of agent configuration files.
When running more then one Sensu server, are people using a single Reddis database, or installing Reddis on each sensu server?