[rabbitmq-discuss] How to use federation with clustering for best HA-behaviour?

Tim Watson tim at rabbitmq.com
Thu Jan 17 12:52:16 GMT 2013

Hi  Adam
On 17 Jan 2013, at 12:39, Adam Aquilon wrote:
> In the federation plugin docs (http://www.rabbitmq.com/federation.html)
> it says:
> "ha-policy
> Determines the "x-ha-policy" argument for the upstream queue (see expires). This is only of interest when connecting to old brokers which determine queue HA mode using this argument. Default is 'none', meaning the queue is not HA."
> So what it says is not entirely true -- you also need it for "federation
> HA" behaviour.

If I'm not mistaken then this won't work when the upstream broker is running a 3.x version. You'll need to enable x-ha-policy *on the broker* as passing this as a queue argument no longer works.  

> BTW, you wouldn't happen to have some tips on how to do upgrades without
> downtime?
> I've studied the documentation for clustered installations and it seems
> you don't use the Erlang facilities for 'upgrading on the fly' and that
> any upgrade *will* require downtime. (A problem for any company, but
> especially for a large one...)

There isn't any support for this at the moment and I don't know of any plans to do so. A load balancer and warm standby using HA is probably the simplest way to deal with this.

More information about the rabbitmq-discuss mailing list