RabbitMQ version Upgrade from 3.6.X to 3.8.X

[Shyamkumar Chauhan]

Hi,

Can I do a direct "Full Cluster Upgrade" from 3.6.X version to 3.8.X version ?

OR

Do i need to do a two step upgrade process , like 3.6.X to 3.7.X and then to 3.8.X . ?

How the Erlang upgrade should be handled during RabbitMQ upgrade ? should it be done before upgrading RabbitMQ or can be done post upgradation of RabbitMQ ?

is Erlang versin "22.3.4.1-2" supported with RabbitMQ 3.8.4 version ?

Thanks,

Shyam

[Wesley Peng]

Hi

If you have no data in RMQ, it should be safe to upgrade from 3.8.2 to 3.8.4 online.

At least I have no issue when did this upgrading in my ubuntu system.

Once you have upgraded RMQ, you could then upgrade erlang OTP from 22 to 23.

My running case:

OS PID: 12797
OS: Linux
Uptime (seconds): 1136430
RabbitMQ version: 3.8.4
Node name: rabbit@ubuntu
Erlang configuration: Erlang/OTP 23 [erts-11.0.2] [source] [64-bit] [smp:1:1] [ds:1:1:10] [async-threads:64]
Erlang processes: 444 used, 1048576 limit
Scheduler run queue: 1
Cluster heartbeat timeout (net_ticktime): 60

Regards.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/d173da7b-c0da-4cfa-a446-236b53842574o%40googlegroups.com.

[Shyamkumar Chauhan]

Hi Wesley,

I believe your upgrade was from 3.8.2 to 3.8.4 which is quite possible as online rolling upgrade.

but i was more curious to know about upgrade from 3.6.X to 3.8.X , is a direct full cluster upgrade possible ?

https://www.rabbitmq.com/upgrade.html#rabbitmq-cluster-configuration

The above link says "YES" but this line "When an upgrade jumps multiple release series (e.g. goes from 3.4.x to 3.6.x), it may be necessary to perform an intermediate upgrade first. "  raises a doubt to me ?

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/CAEsfSa0Wg6_WHQ-KncbqRGsU5n9EpRh0tBWzOzRxQMNFJk7GUg%40mail.gmail.com.

[Wesley Peng]

Just my thought: The software and running status should have no problem, but the configuration (especially the customized configuration) and data you kept in RMQ should possible have problem when jump multiple release series.

Anyway you could implement the test upgrading in a test environment.

Regards.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/CAKsm-ztQfhGuHENrVprXhmh-stsi7rXzngBe1acT_njoUU9U4g%40mail.gmail.com.

[Kushagra Bindal]

Hi Shyam,

Yes, you can directly upgrade from 3.6.x to 3.8.x without any issue.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/CAEsfSa3z6Loan-%3DmKut-Er-FkuTFQsmt6jDBDcP4U_D1d_gQCA%40mail.gmail.com.

[Michael Klishin]

[1] has a table that mentions oldest and newest Erlang/OTP version supported by various (reasonably recent) RabbitMQ releases [1].

There is a dedicated upgrade guide [2] and every release has upgrade notes [3] that to this day mention upgrading from certain older Erlang or RabbitMQ release series, e.g. Erlang before 21

or RabbitMQ before 3.7.0 [3].

Going from 3.6 to 3.8 can be fine but this will be a cluster-wide shutdown because 3.6 does not have support for mixed version clusters. There is also no

single Erlang version that supports both series, so you will have to upgrade Erlang at the same time.

1. https://www.rabbitmq.com/which-erlang.html

2. https://www.rabbitmq.com/upgrade.html

3. https://github.com/rabbitmq/rabbitmq-server/releases/tag/v3.8.5