> Thankyou for acknowledging this!
Indeed! We stopped using RabbitMQ for this reason. Actually, for a number of reasons (its slowness being another major one), but this was the biggy. As a fault tolerant system it doesn't tolerate faults very well at all; we just could not find a way of keeping it stable for long periods, so it had to go.
Re:RabbitMQ Internals
by tokenizerrr on Thursday January 28, 2016 @07:35PM
(#10992688)
What do you use instead?
I wrote my own built on Redis and the StackExchange.Redis client. Then created an actor-system layer on top of that.
It's called LanguageExt.Process and is part of my LanguageExt project:
Kafka
Thankyou for acknowledging this! The mirroring is functionally not a very useful HA/horizontal scale feature until this is sorted. Mnesia has the same problem, so one has to imagine that the root cause is Mnesia.
Running RabbitMQ in production for large scale OpenStack deployments, I have actually started to recommend a singleton RabbitMQ instance because the mirroring can cause all kinds of emergent behaviour during a network partition.
OTOH, RabbitMQ does handle OpenStack at scale very well when there are no partitions, which is no mean feat, so kudos and thankyou.