A rolling restart is enough. Just stop one server ,replace jar, restart, and it will join back the quorum. Then do this for the rest of the servers.
Update requires a restart, but you can save yourself a full restart this way. You will have no downtime. Regards, Norbert On Wed, Sep 12, 2018 at 3:05 PM rammohan ganapavarapu < rammohanga...@gmail.com> wrote: > Norbert, > > Thank you, do we need to restart process after jar replacement? > > Ram > > On Wed, Sep 12, 2018, 12:56 AM Norbert Kalmar <nkal...@cloudera.com.invalid > > > wrote: > > > Hi, > > > > We had a discussion about this not long ago, it was 3.4.8 to 3.4.13, but > > same things have to be done in this case. > > > > > http://zookeeper-user.578899.n2.nabble.com/How-to-upgrade-zookeeper-from-3-4-8-to-3-4-13-td7583831.html > > > > If you just replace the jar, you don't even have to copy anything else. > > > > > > Regards, > > Norbert > > > > On Wed, Sep 12, 2018 at 12:29 AM rammohan ganapavarapu < > > rammohanga...@gmail.com> wrote: > > > > > I have zk cluster with 3.4.5 version and planing to upgrade to 3.4.13 > > > version, can some one point me to a upgrade steps? When i copy snapshot > > > from 3.4.5 node to 3.4.13 node it seems to be working but not sure what > > is > > > the proper way of upgrading existing cluster. > > > > > > Thanks, > > > Ram > > > > > >
