[rabbitmq-discuss] Q replication anxiety

Ben Hood 0x6e6562 at gmail.com
Thu Feb 5 23:18:31 GMT 2009


On Wed, Feb 4, 2009 at 5:01 PM, Ben Hyde <bhyde at pobox.com> wrote:
> This is causing me anxiety:  "... All data/state required for the
> operation of a RabbitMQ broker is replicated across all nodes ...
> exception to this are message queues, which currently only reside on
> the node that created them ..."[1]

Which is the reason why we write it on the box so there can be no
misconception about the things that RabbitMQ guarantees. The
persistence guarantee depends on a journal that resides on reliable
block storage. We're thinking about reliablity through replication,
but because it costs a lot, these thoughts have been deprioritized.

> My setup is on ec2.   My testing randomly kill's machines; in service
> of assuring the system can self heal.  Obviously I'm going to be
> miserable if I kill the machines with Q's on them?  I guess i need to
> be sure the disks the Q's fall onto aren't wiped (which they are today).

You'll have to wait for the cloud guys to respond to this. I know that
that EC2 brought out EBS a while back, however, I don't know what
implications this has for Rabbit.


More information about the rabbitmq-discuss mailing list