As of now we are taking care of upgrading your entire cluster at once when you want to move to a new Erlang or RabbitMQ version. These options are now only available for the entire cluster, and not per node as before. This will ensure that you don't end up with a misconfigured cluster that has incompatible version installed on the nodes.
All nodes must run the same Erlang version, so an Erlang cluster upgrade will lead to at least 1 minute downtime for the cluster (depending on the number of mirrored queues, persistent messages etc.).
Nodes can run different patch versions of RabbitMQ, so when upgrading between patch
versions we do a rolling upgrade, taking down only one node at the time.
Upgrading between minor or major versions will result in some downtime, as with Erlang upgrades.
Note that if you have custom plugins installed this automated upgrade won't work. If this is the case and you want to upgrade please use the email below.
Please email us at email@example.com if you have any suggestions or feedback.