alexlovelltroy
commented
9 years ago We're working on replacing the redis in the sensu instance with an elasticache redis which should enable us to do this. See issue #14 While we're at it, we should do the same for flapjack.
I think it would be interesting to have at least two sensu-server nodes for several reasons, one of which is that this server is the core of notifications, but it would also allow for easier maintenance of this part of the stack. Sensu works well in cluster. It's able to spread out health checks events on multiple nodes automatically, spreading out load in large installations. Graphite and rabbitmq are already clustered, and I also saw some efforts for switching from redis to elasticache (I really like to use "redishappy" to manage redis clusters in non AWS environments). I think the sensu-server deserves its own cluster too!