issue upgrading a cluster from 3.6.12 to 3.7.1

153 views
Skip to first unread message

Chen Wei Hsu

unread,
Dec 30, 2017, 12:13:40 PM12/30/17
to rabbitmq-users
Hi,

I have a cluster with 3 nodes of rabbitmq 3.6.12(erlang 18), and I want to upgrade them to rabbitmq 3.7.1(erlang 20).
I stop one node upgrade it to 3.7.1(erlang 20), but in the log it told me the following message.

2017-12-31 01:00:07.131 [info] <0.33.0> Application lager started on node rabbit@rabbit1
2017-12-31 01:00:07.134 [info] <0.5.0> Log file opened with Lager
2017-12-31 01:00:07.866 [error] <0.5.0> Cluster upgrade needed but other nodes are running [add_opts_to_listener,cluster_name,exchange_event_serial,gm,internal_system_x,mirrored_supervisor,policy_apply_to,policy_version,remove_user_scope,semi_durable_route,topic_trie,topic_trie_node,user_admin_to_tags,user_password_hashing]

I cannot start the new node, but the two others are alive and still running 3.6.12. It looks like some configs are incompatible. 
So what should I do now to upgrade all nodes to 3.7.1?

Michael Klishin

unread,
Dec 30, 2017, 12:54:19 PM12/30/17
to rabbitm...@googlegroups.com
3.6 to 3.7 upgrade cannot be a rolling one. You must shut down and upgrade all nodes, then start them. Or set up a new
cluster, export/import definitions there and switch your apps.

--
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-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
MK

Staff Software Engineer, Pivotal/RabbitMQ

Chen Wei Hsu

unread,
Dec 30, 2017, 8:26:15 PM12/30/17
to rabbitmq-users
I see. Thanks!


On Sunday, December 31, 2017 at 1:54:19 AM UTC+8, Michael Klishin wrote:
3.6 to 3.7 upgrade cannot be a rolling one. You must shut down and upgrade all nodes, then start them. Or set up a new
cluster, export/import definitions there and switch your apps.
On Sat, Dec 30, 2017 at 5:13 PM, Chen Wei Hsu <cwhs...@gmail.com> wrote:
Hi,

I have a cluster with 3 nodes of rabbitmq 3.6.12(erlang 18), and I want to upgrade them to rabbitmq 3.7.1(erlang 20).
I stop one node upgrade it to 3.7.1(erlang 20), but in the log it told me the following message.

2017-12-31 01:00:07.131 [info] <0.33.0> Application lager started on node rabbit@rabbit1
2017-12-31 01:00:07.134 [info] <0.5.0> Log file opened with Lager
2017-12-31 01:00:07.866 [error] <0.5.0> Cluster upgrade needed but other nodes are running [add_opts_to_listener,cluster_name,exchange_event_serial,gm,internal_system_x,mirrored_supervisor,policy_apply_to,policy_version,remove_user_scope,semi_durable_route,topic_trie,topic_trie_node,user_admin_to_tags,user_password_hashing]

I cannot start the new node, but the two others are alive and still running 3.6.12. It looks like some configs are incompatible. 
So what should I do now to upgrade all nodes to 3.7.1?

--
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 post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages