[rabbitmq-discuss] If 2 nodes out a 3 node cluster, the third one becomes unresponsive until one of the nodes is brought back.

Wed Aug 7 15:21:33 BST 2013

I can reproduce this very reliably.

How can I run an instrumented version?

On Wed, Aug 7, 2013 at 5:32 AM, Emile Joubert <emile at rabbitmq.com> wrote:

> On 06/08/13 17:53, Yamil Einar Asusta Santos wrote:
>
> > I have put the log in
> > here: https://gist.github.com/elbuo8/e5171ec85608b7bd7842
>
> The error recorded on 6-Aug-2013::16:29:44 looks like it might be part
> of the problem. Can you tell by looking at the other logfiles whether
> anything noteworthy happened at that time? Is anything recorded in the
> sasl log?
>
> Are you able to reproduce this issue reliably? And does the last
> remaining node always have an log entry containing
> "{rabbit_node_monitor,handle_info,2}" ?
>
> Would it be possible for you to run an instrumented version of the
> broker to help discover the cause of the problem? It will help alot if
> you can reproduce the problem with instrumented code in a test environment.
>
> You may wish to configure "cluster_partition_handling" to "ignore" as a
> temporary workaround. This should allow the last node to keep running
> while the others are off-line.
>
>
>
>
> -Emile
>
>
>
>
>

-- 
Yamil Asusta
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130807/42a18c08/attachment.htm>