From ce1512a3fdc429746dbd1085e248ddd1c2f28e05 Mon Sep 17 00:00:00 2001 From: Michal Kuratczyk Date: Wed, 30 Oct 2024 12:58:35 +0100 Subject: [PATCH] Abort restart-cluster if something goes wrong For example, if the first restarted node doesn't start, don't try to restart the other nodes. This mimics what orchestrators such as Kubernetes or BOSH would do (although they perform this check differently) (cherry picked from commit 2c0fc70135820a0381c3580424964fa16c224b2b) (cherry picked from commit 0266a8eb379d2cb9b752f60c9e7cc4c3f99b921b) --- deps/rabbit_common/mk/rabbitmq-run.mk | 1 + 1 file changed, 1 insertion(+) diff --git a/deps/rabbit_common/mk/rabbitmq-run.mk b/deps/rabbit_common/mk/rabbitmq-run.mk index 083d624cc29..71179295196 100644 --- a/deps/rabbit_common/mk/rabbitmq-run.mk +++ b/deps/rabbit_common/mk/rabbitmq-run.mk @@ -436,6 +436,7 @@ restart-cluster: -rabbitmq_prometheus tcp_config [{port,$$((15692 + $$n - 1))}] \ -rabbitmq_stream tcp_listeners [$$((5552 + $$n - 1))] \ "; \ + $(RABBITMQCTL) -n "$$nodename" await_online_nodes $(NODES) || exit 1; \ done; \ wait