RabbitMQ Internals

by blopeur • 10 years ago

253 12 10 years ago

jvehent2• 10 years ago

This is cool! RabbitMQ could really use better documentation. I had to implement permissions for MIG a while ago, and it tooks many trials and errors to get it right. https://github.com/mozilla/mig/blob/master/tools/create_rabb...

nitrogen• 10 years ago

I found RabbitMQ's docs to be pretty useful myself, as long as you are familiar with regular expressions. I set up a system with fewer users and simpler permissions though. Out of curiosity, what did you find lacking?

jvehent2• 10 years ago

Use cases and examples are pretty scarce. The doc is accurate, but understand the doc for a newcomer to the tool is difficult.

redwards510• 10 years ago

This will be helpful in understanding this framework I found yesterday called RestBus[1]. From their site: "RestBus is a high performance messaging library that enables you to consume ASP.NET Core, Web API and ServiceStack service endpoints via RabbitMQ".

[1] http://restbus.org/

elcct• 10 years ago

Oh that is so sweet. I was looking for something to read for bed time and this is perfect. Thanks!

blorgle• 10 years ago

"Finally, GM is not at all designed to cope with partial network partitions: if A is partitioned from B, then B can remove it from Mnesia, and that information can leak back to A via C. We currently don't handle this situation well; this is the biggest unsolved problem in RabbitMQ."

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.

louthy2• 10 years ago

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.

tokenizerrr• 10 years ago

What do you use instead?

RabbitMQ Internals

Related Stories