From 148453f415637dd2dbbe4847fd9dff17632c14d3 Mon Sep 17 00:00:00 2001 From: Clark Boylan Date: Mon, 31 Oct 2022 09:28:32 -0700 Subject: [PATCH] Upgrade our zookeeper cluster to 3.6 Since we are already running zk 3.5 the upgrade to 3.6 should be able to happen in a rolling fashion just like 3.5 minor upgrades. This change will test that our configs work with 3.6. If they do we should be able to land this then watch the automation automatically upgrade things for us. An alternative would be to put zk04/5/6 into the emergency file and manually do this then land this change and remove the hosts from the emergency file. I'm happy to do this process as well assuming others prefer it. One reason to do things this way is that zk05 is the current leader and we might want to do it last instead of second. Change-Id: Ifc823fdbc4ad40e2cf1235ac9100663918fb413d --- .../roles/zookeeper/files/zookeeper-compose/docker-compose.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/playbooks/roles/zookeeper/files/zookeeper-compose/docker-compose.yaml b/playbooks/roles/zookeeper/files/zookeeper-compose/docker-compose.yaml index 466e0becad..d4c2b1076e 100644 --- a/playbooks/roles/zookeeper/files/zookeeper-compose/docker-compose.yaml +++ b/playbooks/roles/zookeeper/files/zookeeper-compose/docker-compose.yaml @@ -4,7 +4,7 @@ version: '2' services: zk: - image: docker.io/library/zookeeper:3.5 + image: docker.io/library/zookeeper:3.6 restart: always network_mode: host user: "10001:10001"