Rabbit: Eradicate potential crashes in wait job while upgrading cluster
When upgrading/reconfiguring a rabbit cluster its possible that the nodes will not return the cluster status for some time, this ps allows us to cope with this much more gracefully than simply crashing a few times, before proceeding. Change-Id: Ibf525df9e3a9362282f70e5dbb136430734181fd Signed-off-by: Pete Birley <pete@port.direct>
This commit is contained in:
parent
2c8b18aeb8
commit
af270934d4
@ -59,6 +59,10 @@ function sorted_node_list () {
|
||||
if test "$(active_rabbit_nodes)" -gt "$RABBIT_REPLICA_COUNT"; then
|
||||
echo "There are more nodes registed in the cluster than desired, pruning the cluster"
|
||||
PRIMARY_NODE="$(sorted_node_list | awk '{ print $1; exit }')"
|
||||
until rabbitmqctl -l -n "${PRIMARY_NODE}" cluster_status >/dev/null 2>&1 ; do
|
||||
echo "Waiting for primary node to return cluster status"
|
||||
sleep 10
|
||||
done
|
||||
echo "Current cluster:"
|
||||
rabbitmqctl -l -n "${PRIMARY_NODE}" cluster_status
|
||||
NODES_TO_REMOVE="$(sorted_node_list | awk "{print substr(\$0, index(\$0,\$$((RABBIT_REPLICA_COUNT+1))))}")"
|
||||
|
Loading…
Reference in New Issue
Block a user