[rabbitmq-discuss] What happens during a network partition?

[Chris Nicel]

Hi Michael,

Thanks for the info. Not sure why I couldn't find those pages on your website.

I will pass this info on to our hosting provider. Hopefully they will shed some light on it.

Cheers

Chris

-----Original Message-----
From: Michael Klishin [mailto:mklishin at gopivotal.com]
Sent: 06 June 2014 14:37
To: Chris Nicel; Discussions about RabbitMQ
Subject: Re: [rabbitmq-discuss] What happens during a network partition?

On 6 June 2014 at 17:11:10, Chris Nicel (chris.nicel at 15below.com) wrote:
> >
> What happens in the event of a network partition?

See http://www.rabbitmq.com/partitions.html and http://www.rabbitmq.com/ha.html.

> Curiously there is nothing else in the logs on zmq2 @ 12:15

Network partitions can be asymmetrical: node A can connect to B but B can't connect to A. Or they don't detect connectivity loss at the same time. So this is not necessarily an indication of something unusual .
--
MK

Software Engineer, Pivotal/RabbitMQ

 15below Limited: Company registered in England and Wales No 3945289
Registered Office: Lyndean House, 43-46 Queens Road, Brighton BN1 3XB, United Kingdom

15below Australia Pty Limited: ABN 25 132 716 379
Level 21, Tower 2 Darling Park, 201 Sussex Street, Sydney, NSW 2000, Australia

Please think about the environment before printing this email.

************************************************************************
This email and any attachments may be confidential and/or legally privileged and are solely for the use of the intended recipient.  If you have received this email in error please contact the sender.  Any views or opinions expressed within this e-mail are solely those of the sender, and do not necessarily represent those of 15below unless otherwise specifically stated.  Although 15below has taken every reasonable precaution to ensure that any attachment to this e-mail has been checked for viruses, it is strongly recommended that you carry out your own virus check before opening any attachment, as we cannot accept liability for any damage sustained as a result of software virus infection.