[rabbitmq-discuss] Monitor and restart
tim at rabbitmq.com
Wed Jul 10 11:09:44 BST 2013
On 8 Jul 2013, at 16:21, Jorge Diz Pico wrote:
> I peeked around and noticed Rabbit is not using heart, which makes me unease about potential crashes. I tried to tweak the start scripts myself but it's not as straight-forward as it would seem to make it work.
So you can indeed add some settings to RABBITMQ_SERVER_ERL_ARGS when starting up (or set these in the rabbitmq user's default environment) and of course you'll need to set the HEART_COMMAND environment variable to whatever command you normally use to start the broker (depending on how you installed it).
> So before I make a mess of it, I'd like to know if there's any reason why Rabbit doesn't use heart or even offer a quick flag to enable it (at least I couldn't find any reference to it). Does it use any other mechanism underneath to ensure reliability?
There are a couple of reasons we don't do this out of the box.
1. it would be fiddly to set this up in a packaged install for all possible environments
2. there's a plethora of other generic options out there (such as monit, god, etc)
3. automatically restarting a clustered node could have unintended consequences, depending on how it died
In short, by all means turn heart on if you like, but if I were you I'd consider looking at other generic options too. And make sure you understand what the potential consequences of automatic restart might be, for example if several clustered nodes go offline together, the order in which they're restarted can be important.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss