From user-return-12863-archive-asf-public=cust-asf.ponee.io@zookeeper.apache.org Mon Jun 22 10:51:05 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 719C118057A for ; Mon, 22 Jun 2020 12:51:05 +0200 (CEST) Received: (qmail 23625 invoked by uid 500); 22 Jun 2020 10:51:03 -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 Received: (qmail 23599 invoked by uid 99); 22 Jun 2020 10:51:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jun 2020 10:51:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id A2ECE1A3187 for ; Mon, 22 Jun 2020 10:51:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.752 X-Spam-Level: * X-Spam-Status: No, score=1.752 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_REPLY=1, HTML_MESSAGE=0.2, KAM_NUMSUBJECT=0.5, NUMERIC_HTTP_ADDR=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, WEIRD_PORT=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-he-de.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 4CyrQvVwre1r for ; Mon, 22 Jun 2020 10:50:59 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2a00:1450:4864:20::243; helo=mail-lj1-x243.google.com; envelope-from=kuldeep.singh08@gmail.com; receiver= Received: from mail-lj1-x243.google.com (mail-lj1-x243.google.com [IPv6:2a00:1450:4864:20::243]) by mx1-he-de.apache.org (ASF Mail Server at mx1-he-de.apache.org) with ESMTPS id EC0147DCB0 for ; Mon, 22 Jun 2020 10:50:58 +0000 (UTC) Received: by mail-lj1-x243.google.com with SMTP id x18so18718871lji.1 for ; Mon, 22 Jun 2020 03:50:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=aAw/eU+yCRTN2qgXzsj02oRtgbQvQGPGMl7tJo3jJn8=; b=u9da+q3XpYJwwFLTi5aMTGPZ4BrWX6iZ/Qj2Llovl5kQrbs2iwV81HmeDO8dCel8wd dmWm0lfpXsGDaVDbEZRJCXt1XupJF02uHJt6iX2poiZLz8Jwg41X8A/zjOKlm38/tC7v oKPrHZOw4czm5LEKaHSNa0nW+NmI1xWdH5hnOC6K3os2tCjMID1Q3Pg40Q0J+9GgOiFX eYJmfV9dm8k7ncDlKwjovY6T8aUIn/kpgzHTnrkTspjGpeEPtHnA68zz8I23dVP/N0w8 wna4RbrspjHaXYcrJi4w24YEOE1O/7gtohhdDt/bqlipKnZrbBxg1JTUFLpDa09XFPoG yEiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=aAw/eU+yCRTN2qgXzsj02oRtgbQvQGPGMl7tJo3jJn8=; b=qtr0dsGmYmZasbL19DMWwLOS0C5Du1DQZ/gWPbu9k6A1Tf1GL+vGe3SU0oqCAkwhTJ dha5ciw3qZlH9+bTCve/rdfk6mLXDAixm3XSDgLgBpcw3EgCTpPVvXNDP+zvTnXFQyLn P94X2MuYS2QLftksPnUagsh+KwEmRdIvfe9sHTGaG82v/SxePQdhjBFZErm2vp6pxzOP 1EfglIbBpnbH7GUIxBte9hbV78gFhyDLquqDctkynYdMfIsRSnxLlYnhlDFlkdDaDo2N yPbhwgk56N5CZmusjBo2arjUiTkDHshYWscXa+SbWRXla7k7AHmb6iyLxRfBsgpL3JaL F8Jw== X-Gm-Message-State: AOAM532d+vsJtKLm7D51H2zviJt3x5IyLUDyKbZOUgU6/3fVMrP4OH74 X1ZsHsFb2t+Mr11TWc84smDsFTQJqhpeKUakhROtkZX7 X-Google-Smtp-Source: ABdhPJy3hamhuROYHgD+a+oVRJZJX0475wW8+5uD+iiNZ5kvIVc6gGApegx/KgUikZOUcuK9z/NPS3QifqHxKQvc7r8= X-Received: by 2002:a2e:9586:: with SMTP id w6mr7732936ljh.318.1592823057411; Mon, 22 Jun 2020 03:50:57 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: kuldeep singh Date: Mon, 22 Jun 2020 16:20:18 +0530 Message-ID: Subject: Re: upgrade from 3.4.5 to 3.5.6 To: user@zookeeper.apache.org Content-Type: multipart/alternative; boundary="00000000000086f25505a8aa04d9" --00000000000086f25505a8aa04d9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Team, How we will do secure communication between the Curator framework and zookeeper 3.5.6 ? I didn't get any solution right now. I appreciate it if someone could help me with the same. Thanks, --------------------- Kuldeep Singh Budania Software Architect On Fri, Apr 17, 2020 at 4:53 PM Szalay-Bek=C5=91 M=C3=A1t=C3=A9 wrote: > Hello Kuldeep, > > did you download the source from the ZooKeeper webpage, or checked out fr= om > git? > Anyway, the following commands should work: > > wget > > https://downloads.apache.org/zookeeper/zookeeper-3.5.7/apache-zookeeper-3= .5.7.tar.gz > tar xzvf ./apache-zookeeper-3.5.7.tar.gz > cd apache-zookeeper-3.5.7 > mvn clean install -DskipTests > > I tested it with OpenJDK 8u424 and maven 3.6.0. > > Kind regards, > Mate > > > On Fri, Apr 17, 2020 at 12:51 PM kuldeep singh > wrote: > > > Hi All, > > > > I have download the zookeeper source code and run the mvn command for > > packaging but get problem on "zookeeper-server" directory. > > > > *command :- mvn clean package* > > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile > > (default-compile) on project zookeeper: Fatal error compiling: > > java.lang.NullPointerException -> [Help 1] > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execu= te > > goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile > > (default-compile) on project zookeeper: Fatal error compiling > > at > > > > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.jav= a:216) > > at > > > > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.jav= a:153) > > at > > > > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.jav= a:145) > > at > > > > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(L= ifecycleModuleBuilder.java:108) > > at > > > > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(L= ifecycleModuleBuilder.java:76) > > at > > > > > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreaded= Builder.build(SingleThreadedBuilder.java:51) > > at > > > > > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleSta= rter.java:116) > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:36= 1) > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) > > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) > > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > > > > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java= :62) > > at > > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI= mpl.java:43) > > at java.lang.reflect.Method.invoke(Method.java:498) > > at > > > > > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher= .java:289) > > at > > > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:22= 9) > > at > > > > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launch= er.java:415) > > at > > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:35= 6) > > Caused by: org.apache.maven.plugin.MojoExecutionException: Fatal error > > compiling > > at > > > > > org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCom= pilerMojo.java:1140) > > at > > > > > org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:1= 88) > > at > > > > > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuil= dPluginManager.java:133) > > at > > > > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.jav= a:208) > > ... 19 more > > Caused by: org.codehaus.plexus.compiler.CompilerException: > > java.lang.NullPointerException > > at > > > > > org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(Ja= vaxToolsCompiler.java:173) > > at > > > > > org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacComp= iler.java:174) > > at > > > > > org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCom= pilerMojo.java:1129) > > ... 22 more > > Caused by: java.lang.RuntimeException: java.lang.NullPointerException > > at com.sun.tools.javac.main.Main.compile(Main.java:559) > > at > > com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:129) > > at > > com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:138) > > at > > > > > org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(Ja= vaxToolsCompiler.java:126) > > ... 24 more > > Caused by: java.lang.NullPointerException > > at > > > > > com.sun.tools.javac.model.JavacTypes.getOverriddenMethods(JavacTypes.java= :306) > > at com.sun.tools.doclint.Env.setCurrent(Env.java:155) > > at com.sun.tools.doclint.Checker.scan(Checker.java:144) > > at com.sun.tools.doclint.DocLint$2.visitDecl(DocLint.java:285) > > at > > com.sun.tools.doclint.DocLint$DeclScanner.visitClass(DocLint.java:359) > > at > > com.sun.tools.doclint.DocLint$DeclScanner.visitClass(DocLint.java:346) > > at > > com.sun.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:720) > > at > > com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:68) > > at > > com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:81) > > at > > com.sun.source.util.TreeScanner.visitNewClass(TreeScanner.java:280) > > at > > com.sun.tools.javac.tree.JCTree$JCNewClass.accept(JCTree.java:1532) > > at > > com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:68) > > at > > com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:81) > > at > > com.sun.source.util.TreeScanner.visitVariable(TreeScanner.java:153) > > at > > com.sun.tools.doclint.DocLint$DeclScanner.visitVariable(DocLint.java:37= 3) > > at > > com.sun.tools.doclint.DocLint$DeclScanner.visitVariable(DocLint.java:34= 6) > > at > > com.sun.tools.javac.tree.JCTree$JCVariableDecl.accept(JCTree.java:864) > > at > > com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:68) > > at > > com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:81) > > at com.sun.source.util.TreeScanner.scan(TreeScanner.java:91) > > at > > com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:99) > > at > com.sun.source.util.TreeScanner.visitClass(TreeScanner.java:133) > > at > > com.sun.tools.doclint.DocLint$DeclScanner.visitClass(DocLint.java:360) > > at > > com.sun.tools.doclint.DocLint$DeclScanner.visitClass(DocLint.java:346) > > at > > com.sun.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:720) > > at > > com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:68) > > at com.sun.source.util.TreeScanner.scan(TreeScanner.java:91) > > at > > com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:99) > > at > > > com.sun.source.util.TreeScanner.visitCompilationUnit(TreeScanner.java:120= ) > > at > > > > > com.sun.tools.doclint.DocLint$DeclScanner.visitCompilationUnit(DocLint.ja= va:354) > > at > > > > > com.sun.tools.doclint.DocLint$DeclScanner.visitCompilationUnit(DocLint.ja= va:346) > > at > > com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:55= 0) > > at > > com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:68) > > at com.sun.tools.doclint.DocLint$3.started(DocLint.java:296) > > at > > > > > com.sun.tools.javac.api.ClientCodeWrapper$WrappedTaskListener.started(Cli= entCodeWrapper.java:668) > > at > > > > > com.sun.tools.javac.api.MultiTaskListener.started(MultiTaskListener.java:= 103) > > at > > com.sun.tools.javac.main.JavaCompiler.attribute(JavaCompiler.java:1240) > > at > > com.sun.tools.javac.main.JavaCompiler.compile2(JavaCompiler.java:901) > > at > > com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:860) > > at com.sun.tools.javac.main.Main.compile(Main.java:523) > > ... 27 more > > [ERROR] > > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > > [ERROR] > > [ERROR] For more information about the errors and possible solutions, > > please read the following articles: > > [ERROR] [Help 1] > > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > > > > Can someone help me on this issue? > > > > Thanks, > > --------------------- > > Kuldeep Singh Budania > > > > > > > > On Sat, Apr 4, 2020 at 5:57 PM Szalay-Bek=C5=91 M=C3=A1t=C3=A9 < > > szalay.beko.mate@gmail.com> > > wrote: > > > > > these exceptions can mean many things... I think this can be even > normal > > > duding rolling restart (as some connections get broken in this case) > > > > > > However, I saw cases already when exceptions like these killed receiv= er > > or > > > sender threads in QuorumCnxManager / Leader Election in such a way th= at > > > they were not able to recover, so the node was unable to connect to a= ny > > > quorum until restart. I remember seeing this in 3.4 too. > > > > > > Do you see these exceptions in the second server (the one which you > just > > > upgraded in step 3)? > > > Is this issue reproducible? > > > > > > What is the tickTime and initLimit you use? Maybe the server just > require > > > more time to sync? > > > > > > I would need more logs to really see what happened. Can you create a > Jira > > > issue and upload the logs and also the ZooKeeper configs? I am happy = to > > > take a closer look. > > > (if you need to re-run the test to collect the logs, then enabling > DEBUG > > > logs would be great. The INFO level logs are usually enough for these > > > problems, but one can never know...) > > > > > > Kind regards, > > > Mate > > > > > > > > > On Fri, Apr 3, 2020 at 10:05 AM kuldeep singh < > kuldeep.singh08@gmail.com > > > > > > wrote: > > > > > > > Hi Team, > > > > > > > > I have done some POC on rolling upgrade and found below result. > > > > > > > > > > > > 1. On 1st node upgrade zookeeper . Traffic was running fine > because > > 2 > > > > nodes are already on old zookeeper. > > > > 2. On 1st node upgrade our application and didn=E2=80=99t find a= ny issue > > > > 3. On 2nd node upgrade zookeeper but got below error and zookeep= er > > is > > > > not taking any requests > > > > 4. > > > > > > > > java.io.EOFException > > > > > > > > at java.io.DataInputStream.readInt(DataInputStream.java:392= ) > > > > > > > > at > > > > > > > > > > > > > > org.apache.zookeeper.server.quorum.QuorumCnxManager$RecvWorker.run(Quorum= CnxManager.java:747) > > > > > > > > 2020-03-30 14:19:55,587 - WARN > > > > [RecvWorker:1:QuorumCnxManager$RecvWorker@765] - Interrupting > > SendWorker > > > > > > > > 2020-03-30 14:19:55,588 - ERROR [LearnerHandler-/192.168.44.73:3375= 4 > > > > :LearnerHandler@562] - Unexpected exception causing shutdown while > > sock > > > > still open > > > > > > > > java.io.EOFException > > > > > > > > at java.io.DataInputStream.readInt(DataInputStream.java:392= ) > > > > > > > > at > > > > > org.apache.jute.BinaryInputArchive.readInt(BinaryInputArchive.java:63) > > > > > > > > at > > > > > > > > > > > > > > org.apache.zookeeper.server.quorum.QuorumPacket.deserialize(QuorumPacket.= java:83) > > > > > > > > at > > > > > > > > > > org.apache.jute.BinaryInputArchive.readRecord(BinaryInputArchive.java:108= ) > > > > > > > > at > > > > > > > > > > > > > > org.apache.zookeeper.server.quorum.LearnerHandler.run(LearnerHandler.java= :476) > > > > > > > > 2020-03-30 14:19:55,588 - WARN > > > > [SendWorker:1:QuorumCnxManager$SendWorker@679] - Interrupted while > > > waiting > > > > for message on queue > > > > > > > > Please let me know is this the known issue or this is different iss= ue > > > which > > > > is mention in Apache zookeeper documentation when upgrading from > 3.4.5 > > to > > > > 3.5.6 > > > > > > > > Thanks, > > > > --------------------- > > > > Kuldeep Singh Budania > > > > Software Architect > > > > > > > > > > > > > > > > On Sun, Mar 29, 2020 at 9:06 AM Alexander Shraer > > > > wrote: > > > > > > > > > +1 to what Mate said (I wrote the quoted instructions). > > > > > > > > > > > > > > > > > > > > On Tue, Mar 24, 2020 at 7:03 AM Szalay-Bek=C5=91 M=C3=A1t=C3=A9 < > > > > > szalay.beko.mate@gmail.com> > > > > > wrote: > > > > > > > > > > > Hi Kuldeep, > > > > > > > > > > > > I just want to provide you some background info about our > > > > documentation. > > > > > > The reason to upgrade to 3.4.6 first is to avoid the following > > error: > > > > > > > > > > > > > 2013-01-30 11:32:10,663 [myid:2] - WARN [localhost/ > > 127.0.0.1:2784 > > > > > > :QuorumCnxManager@349] - Invalid server id: -65536 > > > > > > > > > > > > This error comes because of the protocol changes between > ZooKeeper > > > > server > > > > > > nodes during connection initiation for leader election. In > > ZooKeeper > > > > 3.5 > > > > > a > > > > > > protocol version was introduced (see ZOOKEEPER-107) and since > that > > > time > > > > > the > > > > > > fist long value sent in the initial message is not the server I= D > > but > > > > the > > > > > > protocol version (-65536). In ZooKeeper 3.4.6 we made the old 3= .4 > > > > > > ZooKeepers backward compatible, so they are able to parse both > the > > > old > > > > > and > > > > > > the new protocol format (see ZOOKEEPER-1633). This issue happen= s > > only > > > > > when > > > > > > you need to use old (3.4.0 - 3.4.5) and new (3.5.0+) ZooKeeper > > > servers > > > > > > together in the same cluster. During a rolling upgrade, this is > > > usually > > > > > the > > > > > > case to have old and new ZooKeepers present together. > > > > > > > > > > > > The fact that you haven't seen any issues might be caused by th= e > > > order > > > > of > > > > > > the servers. In ZooKeeper the connection initiation between the > > > servers > > > > > > during the leader election follows a specific rule. As far as I > > > > remember > > > > > > always the server with the larger ID 'wins the challenge', so i= t > is > > > > > > possible, that the old server didn't need to parse any initial > > > message > > > > > (if > > > > > > it had the largest ID) and this is why you haven't seen the > issue. > > > Also > > > > > > having 2 nodes up from the 3 nodes cluster still makes the > cluster > > > work > > > > > (so > > > > > > you should also check if all the servers are part of the quorum= ). > > > > > > > > > > > > I agree with Enrico and Norbert, the safest and most stable way > is > > > > > upgrade > > > > > > first to 3.4.latest, then go to 3.5.latest. Still, if you don't > see > > > > that > > > > > > you would hit this specific issue (e.g. no "Invalid server id" = in > > the > > > > log > > > > > > files), and all the three servers can handle traffic, then mayb= e > > you > > > > > don't > > > > > > need to upgrade first to 3.4.latest, it is your decision. > > Definitely > > > > you > > > > > > should test it first, as suggested by the others. > > > > > > > > > > > > Kind regards, > > > > > > Mate > > > > > > > > > > > > On Tue, Mar 24, 2020 at 12:29 PM Norbert Kalmar > > > > > > wrote: > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > That guide is to upgrade to 3.5.0, which was an alpha version= . > A > > > lot > > > > > has > > > > > > > changed for the first stable release of 3.5.5 and then a few > > more, > > > > even > > > > > > > rolling upgrade issues have been fixed for 3.5.6. > > > > > > > This is a more up-to-date guide: > > > > > > > > > https://cwiki.apache.org/confluence/display/ZOOKEEPER/Upgrade+FAQ > > > > > > > > > > > > > > If you have done your testing (with prod snapshot!), then you > can > > > > skip > > > > > > 3.4 > > > > > > > latest upgrade, but keep in mind we do our recommendations fo= r > a > > > > > reason. > > > > > > > There were issues reported and/or found during testing. Some > are > > > > fixed > > > > > > with > > > > > > > 3.5.6, some only happens if certain conditions stand > > (IOException: > > > No > > > > > > > snapshot found - mentioned in the guide, fixed in 3.5.6). > > > > > > > > > > > > > > So it is up to you, I would still recommend to do an 3.4 > upgrade > > > > first, > > > > > > if > > > > > > > it's feasible. > > > > > > > > > > > > > > Regards, > > > > > > > Norbert > > > > > > > > > > > > > > On Tue, Mar 24, 2020 at 11:45 AM kuldeep singh < > > > > > > kuldeep.singh08@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > Current Zookeeper version :- 3.4.5 > > > > > > > > Upgraded version :- 3.5.6 > > > > > > > > > > > > > > > > We are not going with 3.5.7. Our final decision is zookeepe= r > > > > version > > > > > is > > > > > > > > 3.5.6 > > > > > > > > as per your reply first we need to move latest version of > > 3.4.x, > > > > like > > > > > > > below > > > > > > > > > > > > > > > > 3.4.5 -> 3.4.14 -> 3.5.6 (Correct me if I am wrong here) > > > > > > > > > > > > > > > > But if We are not facing any problem that i have shared you > > that > > > we > > > > > > have > > > > > > > > set up of 3 node cluster where 2 node are on 3.5.6 version > and > > 1 > > > > node > > > > > > on > > > > > > > > 3.4.5, Everything is running fine and didn't get any issue, > So > > > what > > > > > > other > > > > > > > > problem we can face if we directly move to 3.5.6 > > > > > > > > > > > > > > > > Thanks, > > > > > > > > --------------------- > > > > > > > > Kuldeep Singh Budania > > > > > > > > Software Architect > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Mar 24, 2020 at 3:58 PM Enrico Olivelli < > > > > eolivelli@gmail.com > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi > > > > > > > > > You have to upgrade to latest 3.4.x Zookeeper then you wi= ll > > > > upgrade > > > > > > to > > > > > > > > > 3.5.7. > > > > > > > > > All should run well without issues > > > > > > > > > > > > > > > > > > > > > > > > > > > Enrico > > > > > > > > > > > > > > > > > > Il Mar 24 Mar 2020, 10:18 kuldeep singh < > > > > kuldeep.singh08@gmail.com > > > > > > > > > > > > ha > > > > > > > > > scritto: > > > > > > > > > > > > > > > > > > > Hi Team, > > > > > > > > > > > > > > > > > > > > We are upgrading zookeeper from 3.4.5 to 3.5.6. I have > set > > > up 3 > > > > > > node > > > > > > > > > > cluster where 2 node are on 3.5.6 version and 1 node on > > > 3.4.5. > > > > > > > > > > > > > > > > > > > > Everything is running fine and didn't get any issue on = my > > > > system. > > > > > > > > > > > > > > > > > > > > but I found something on apache site that first we nee= d > to > > > > > upgrade > > > > > > > on > > > > > > > > > > 3.4.6 than we can upgrade to 3.5.6. So is it mandatory > to > > go > > > > on > > > > > > > 3.4.6 > > > > > > > > > > first. > > > > > > > > > > > > > > > > > > > > *Upgrading to 3.5.0* > > > > > > > > > > > > > > > > > > > > Upgrading a running ZooKeeper ensemble to 3.5.0 should = be > > > done > > > > > only > > > > > > > > after > > > > > > > > > > upgrading your ensemble to the 3.4.6 release. Note that > > this > > > is > > > > > > only > > > > > > > > > > necessary for rolling upgrades (if you're fine with > > shutting > > > > down > > > > > > the > > > > > > > > > > system completely, you don't have to go through 3.4.6). > If > > > you > > > > > > > attempt > > > > > > > > a > > > > > > > > > > rolling upgrade without going through 3.4.6 (for exampl= e > > from > > > > > > 3.4.5), > > > > > > > > you > > > > > > > > > > may get the following error: > > > > > > > > > > > > > > > > > > > > 2013-01-30 11:32:10,663 [myid:2] - INFO [localhost/ > > > > > 127.0.0.1:2784 > > > > > > > > > > :QuorumCnxManager$Listener@498] - Received connection > > > request > > > > / > > > > > > > > > > 127.0.0.1:60876 > > > > > > > > > > > > > > > > > > > > 2013-01-30 11:32:10,663 [myid:2] - WARN [localhost/ > > > > > 127.0.0.1:2784 > > > > > > > > > > :QuorumCnxManager@349] - Invalid server id: -65536 > > > > > > > > > > > > > > > > > > > > During a rolling upgrade, each server is taken down in > turn > > > and > > > > > > > > rebooted > > > > > > > > > > with the new 3.5.0 binaries. Before starting the server > > with > > > > > 3.5.0 > > > > > > > > > > binaries, we highly recommend updating the configuratio= n > > file > > > > so > > > > > > that > > > > > > > > all > > > > > > > > > > server statements "server.x=3D..." contain client ports > (see > > > the > > > > > > > section > > > > > > > > > > Specifying > > > > > > > > > > the client port). As explained earlier you may leave th= e > > > > > > > configuration > > > > > > > > > in a > > > > > > > > > > single file, as well as leave the > > > clientPort/clientPortAddress > > > > > > > > statements > > > > > > > > > > (although if you specify client ports in the new format= , > > > these > > > > > > > > statements > > > > > > > > > > are now redundant). > > > > > > > > > > > > > > > > > > > > Could you please let me know about this case. Appreciat= e > if > > > > > respond > > > > > > > > soon. > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > --------------------- > > > > > > > > > > Kuldeep Singh Budania > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --00000000000086f25505a8aa04d9--