I wrote some custom Chef code that handles a seamless Erlang and RabbitMQ upgrade of a cluster of RabbitMQ reliably. Sadly it's trapped at one company. There's

I wrote some custom Chef code that handles a seamless Erlang and RabbitMQ upgrade of a cluster of RabbitMQ reliably. Sadly it's trapped at one company. There's probably a way to write some code to drain a split brain's data but I suspect nobody has the time to write this code. You could have a process where you block writers to the minority then drain messages and enqueue them on the majority.