From user-return-12928-archive-asf-public=cust-asf.ponee.io@zookeeper.apache.org Mon Sep 7 16:07:42 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mailroute1-lw-us.apache.org (mailroute1-lw-us.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with ESMTPS id 7D74E180181 for ; Mon, 7 Sep 2020 18:07:42 +0200 (CEST) Received: from mail.apache.org (localhost [127.0.0.1]) by mailroute1-lw-us.apache.org (ASF Mail Server at mailroute1-lw-us.apache.org) with SMTP id 8599B12254D for ; Mon, 7 Sep 2020 16:07:41 +0000 (UTC) Received: (qmail 44541 invoked by uid 500); 7 Sep 2020 16:07:40 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Delivered-To: moderator for user@zookeeper.apache.org Received: (qmail 66606 invoked by uid 500); 7 Sep 2020 04:19:19 -0000 Delivered-To: apmail-hadoop-zookeeper-user@hadoop.apache.org X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 5.129 X-Spam-Level: ***** X-Spam-Status: No, score=5.129 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_ALL=1.1, KAM_DMARC_REJECT=3, KAM_DMARC_STATUS=0.01, SPF_FAIL=0.919, SPF_HELO_PASS=-0.001, URIBL_BLOCKED=0.001, URI_HEX=0.1] autolearn=disabled Received-SPF: Fail (mailfrom) identity=mailfrom; client-ip=162.253.133.85; helo=n2.nabble.com; envelope-from=james.gover@canva.com; receiver= Date: Sun, 6 Sep 2020 21:19:08 -0700 (MST) From: James Gover To: zookeeper-user@hadoop.apache.org Message-ID: <1599452348610-0.post@n2.nabble.com> Subject: 3.4.8 to 3.5.8 rolling update MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, We are upgrading from zookeeper 3.4.8 to 3.5.8 via 3.4.14. There are several mentions of going from 3.4.6 to 3.5.8, is going from 3.4.14 to 3.5.8 ok. In terms of Leader-tasks running during the upgrade. The intent is to migrate a cluster of 3 zk nodes by: * scaling up to 5 nodes (adding two new nodes) * one non-leader node at a time; destroying the instance and replacing it with a new 3.5.8 node * then stoping zk on the leader so another node becomes the leader, terminating the instance then adding a 3.5.8 node. * removing two (non-leader) node to scale back to 3 nodes With this process; will leader tasks running on the 3.4.14 leader (using curator leaderLatch) fail when this leader is terminated but succeed if run after a short delay will run on a new 3.5.8 leader node. Thanks, James -- Sent from: http://zookeeper-user.578899.n2.nabble.com/