[rabbitmq-discuss] Queue Failover and restore

Duncan McIntyre dmcintyre at gopivotal.com
Tue Mar 25 09:50:30 GMT 2014

You could use ha-mode nodes to move it to the node you want to be the
master, then change the policy to replicate it again. The disadvantage
being that you risk losing the queue if the master fails before the queue
has been replicated again.

Or, you could use ha-mode nodes to move it around pairs of nodes in the
cluster, until eventually the master was on the node you wanted, and it
will have been replicated at all times.


On Tue, Mar 25, 2014 at 6:39 AM, Michael Klishin <mklishin at gopivotal.com>wrote:

> On 25 March 2014 at 09:59:06, Arun Rao (arunrao.seattle at gmail.com) wrote:
> > > I have 4 nodes with 4 queues on each node. HA policy is set to exactly
> > 2 nodes, so I have exactly one mirror.
> >
> > When a node fails, 4 queues on this node get distributed to the
> > other 3 nodes.
> >
> > After I bring the failed node backup, this failed node now only
> > has mirrors and no queues now live on this failed node. How can
> > I push queues to this failed node without deleting the queue and
> > recreating it?
> >
> > Even after restarting the entire cluster, I dont seem to get my
> > original setup back.
> You can't . Why do you need the queues to be on a specific node?
> --
> MK
> Software Engineer, Pivotal/RabbitMQ
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140325/653744e2/attachment.html>

More information about the rabbitmq-discuss mailing list