[rabbitmq-discuss] cluster upgrade 3.0 -> 3.1 - Downtime.

Emile Joubert emile at rabbitmq.com
Thu Oct 3 09:47:46 BST 2013


Hi,

On 03/10/13 09:27, Santi Nuñez-Cacho wrote:

> rabbitmq documentation claims that downtime is needed because 3.0.1 and
> 3.1.5 cannot be mixed in a cluster.

There are no immediate plans to support seamless upgrades across major
versions.

In general only upgrades between patch versions (e.g. 3.0.x to 3.0.y)
can be performed without downtime. The exceptions are that 3.1.4 and
3.1.5 are not compatible with other older 3.1.x versions in the same
cluster, and 3.0.0 is not compatible with newer versions from the 3.0.x
series.
See https://www.rabbitmq.com/clustering.html#upgrading





-Emile


More information about the rabbitmq-discuss mailing list