[rabbitmq-discuss] Clustered startup with multiple queues and multiple masters
francesco at rabbitmq.com
Thu Jun 21 18:53:05 BST 2012
At Thu, 21 Jun 2012 09:05:05 -0700,
Matt Pietrek wrote:
> Thanks Francesco.
> Your script looks reasonably close to what I'm doing, except for a
> couple of key differences:
> All of your nodes are running on the same host. In my setup, each
> node is in its own VM. I imagine this introduces additional
> networking into the communication between nodes.
Yeah. I'm on my laptop these days, so if anything I'll a VM setup on
> When you start Rabbit instances, you're doing it sequentially. In my
> setup I start up in parallel on all three VMs via Capistrano. If you
> can't go the multi-VM route, you may be able to somewhat simulate
> this by starting the instances with an '&' at the end.
Well, I'm forking them one after the other and then waiting for them
to actually start, so is not that sequential. I doubt that matters.
> I use "killall -9 beam.smp", rather than just "killall beam.smp"
Right. This should not make much of a difference either. I tried with
-9 and things were OK.
As a curiosity, how are you waiting to be sure that the messages are
persisted? I am using publisher confirms, see
http://www.rabbitmq.com/extensions.html - that's why puka and not pika
- but you need to make sure of that, otherwise you can get message
loss or other strange behaviours.
If you are trying to simulate what happens when the system crashes
while sending messages, then it's different and of course you can't
rely on any of the messages in being there when you restart them - but
that does not justify the behaviour you're seeing anyway.
More information about the rabbitmq-discuss