[rabbitmq-discuss] RabbitMQ and network partitions

Simon MacMullen simon at rabbitmq.com
Tue Dec 11 10:44:39 GMT 2012

On 10/12/12 11:12, Tuure Laurinolli wrote:
> Hi,


> After reading http://www.rabbitmq.com/partitions.html I'm somewhat
> concerned about behavior of RabbitMQ upon network partitions. It appears
> that the basic issue is that Mnesia itself prefers availability over
> consistency, and allows update operations even when a node is in
> minority and knows it. It seems that others were concerned about this
> too, and Mnesia now includes "majority" option on tables, which disables
> updates in minority partitions.
> Are there other problems besides Mnesia that cause RabbitMQ to continue
> to operate even in minority partition? If not, would enabling the
> "majority" option on necessary tables in RabbitMQ cause it to continue
> operations in the majority partition and to fail in the minority
> partition, and to keep members of the previous minority partition down
> when connectivity is restored? Presumably the previous minority nodes
> could then be rejoined to the cluster with similar actions as currently.

That's something that we're looking at for a future release. I don't 
think we could enable it by default (lots of people have two node 
clusters) but it might be helpful for some people.

The question of what the minority partition should do when Mnesia 
refuses to perform updates is unclear. Probably it should just shut down 

Cheers, Simon

Simon MacMullen
RabbitMQ, VMware

More information about the rabbitmq-discuss mailing list