[rabbitmq-discuss] Validity of /api/aliveness-test in a clustered environment

Fri Oct 26 21:18:57 BST 2012

Thanks Simon.

Just to make sure I understand fully, does the problem scenario I described
actually occur?

That is, if the aliveness-test queue lives on mq1 and mq1 is unresponsive,
and I then hit the mq2 broker with an /api/aliveness -test request, you'd
expect that request to either time out or take a long time?

Thanks,

Matt

On Fri, Oct 26, 2012 at 3:52 AM, Simon MacMullen <simon at rabbitmq.com> wrote:

> On 26/10/12 01:18, Matt Pietrek wrote:
>
>> If this is an issue, I'm wondering if there are alternative, "approved"
>> manners of checking the health of an individual broker within a cluster?
>>
>
> aliveness-test declares a queue, publishes a message, and basic.gets it.
> You could do that.
>
> Cheers, Simon
>
> --
> Simon MacMullen
> RabbitMQ, VMware
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121026/a520e8f0/attachment.htm>