[rabbitmq-discuss] Monitor and restart

Thu Jul 11 10:25:49 BST 2013

> 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).

That's what I'm trying, but it doesn't work as expected (the rabbit node
immediately crashes during init after being started this way).

> There are a couple of reasons we don't do this out of the box [...]

I understand now, thanks.

> Yes, See http://www.rabbitmq.com/reliability.html

That's internally, but I was looking at it from outside. Some embedded
utility for monitoring its behaviour and knowing it's come down (and
ideally, it would pull itself back up again).

On Wed, Jul 10, 2013 at 12:09 PM, Tim Watson <tim at rabbitmq.com> wrote:

> Hi Jorge,
>
> 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.
>
> Cheers,
> Tim
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130711/37bb9b19/attachment.htm>