<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi,<div><br></div><div>After reading <a href="http://www.rabbitmq.com/partitions.html">http://www.rabbitmq.com/partitions.html</a> 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.</div><div><br></div><div>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.</div><div><br></div><div><br></div></body></html>