<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:10pt">Hi all.<br>I have a three nodes in a cluster deployed on different AWS AZs: A, B and C.<br>The queues are fully mirrored among nodes, the queues are persistent and cluster partition handler is configured to pause-minority. The RabbitMq version I'm using is 3.3.1<br style="" class="">The queues policies are set as: {"ha-mode":"all","ha-sync-mode":"automatic"} .<br><br>I'm bouncing the network connection between two nodes, for instance C and B, in the way that:<br>- A: can reach C and B<br>- C: can reach A<br>- B can reach A<br>In this case, the cluster get stuck and only recovers when all nodes are restarted.<span class="tab"> <br>Is it an expected behavior? </span><br><br>And if I kill one node, instead of only bounce the connection as before, the cluster is
still working.<br>What I think is expected<br><br>Thanks in advance for your time and help<br><br style="" class="">Best Regards,<br>Leo<br><div style="" class=""><br style=""><span style="" class=""></span></div><div style="" class=""> </div><div style="" class=""><span class="" style="font-weight:bold">Leonardo Nogueira de S� Pereira</span><br style="" class="">Tel.: +55 19 3307-5589<br style="" class="">Cel.: +55 19 9122-5943<br style="" class="">Skype: leonardo_pereira_77<br style="" class=""></div></div></body></html>