[rabbitmq-discuss] Queue replication (I know, I know)

Derek Chen-Becker dbecker at cpicorp.com
Wed Oct 20 16:00:27 BST 2010

On 10/20/2010 05:05 AM, Simon MacMullen wrote:
> On 20/10/10 05:14, Derek Chen-Becker wrote:
>> What's more interesting is that if I copy the /var/lib/rabbitmq
>> directory to the backup host *without stopping the primary broker*, and
>> then stop the primary and start the backup, everything still appears to
>> work fine. Now, I suspect that with the low volume I'm pushing here I'm
>> just getting lucky and not copying files in an inconsistent state,
> Probably not. Rabbit is designed to repair queues when it comes up 
> again, so if you're copying queues when they're inconsistent it'll get 
> fixed by the time the backup broker is accepting connections. Of course, 
> if you're unlucky, you could lose a few messages in such a process but 
> from what you've said before it sounds like that isn't your biggest concern?

OK, that helps us a lot. Our main concern is with not having to
retransmit a large time-span of messages, but we can deal with a few
lost ones in the case where the primary broker goes down. Your note on
doing transacted publishes makes sense, so we'll modify our wrappers to
do that. I'm assuming there's some performance overhead with transacted
messages but with the low volume we're talking about that shouldn't be
an issue.

> Hmm, interesting idea. I'll see if we're interested in doing that. We're 
> currently looking at how to make the HA experience better so this might 
> be a possibility.

Thanks, any work to improve HA would be greatly appreciated.


More information about the rabbitmq-discuss mailing list