zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Debraj Manna <subharaj.ma...@gmail.com>
Subject Re: How to upgrade zookeeper from 3.4.8 to 3.4.13?
Date Thu, 30 Aug 2018 10:20:04 GMT
I have removed other zookeeper-<version>.jar and it is working fine.

Thanks,

On Thu, Aug 30, 2018 at 3:48 PM Norbert Kalmar <nkalmar@cloudera.com.invalid>
wrote:

> It's not because of versions. It's due to the fact there are multiple
> zookeeper jar's in the tarball like zookeeper-XY-bin.jar, zookeeper-XY.jar
> etc. (test, sources, javadoc).
>
> I'm not sure why there are so many and some overlap, but this is how it is
> currently. So the script adds all of them to the classpath. But there
> shouldn't be jar files from multiple versions of ZooKeeper present in the
> directory.
>
> Well, at least this is my understanding.
>
>
>
> On Thu, Aug 30, 2018 at 12:01 PM Debraj Manna <subharaj.manna@gmail.com>
> wrote:
>
> > Thanks Norbert for replying.
> >
> > What is the intention of this check *for i in
> "$ZOOBINDIR"/../zookeeper-*.*
> > *jar* ? Do we want to add the latest version first in the CLASSPATH? If
> > that is the case then I think this will fail for versions like 3.4.10
> > onwards if we also have 3.4.8, 3.4.5 etc in that directory?
> >
> > On Thu, Aug 30, 2018 at 3:13 PM Norbert Kalmar
> > <nkalmar@cloudera.com.invalid>
> > wrote:
> >
> > > Hi,
> > >
> > > zkEnv.sh intentionally has the wild card, it's not a bug. As the
> > zookeeper
> > > jar has the version in its name due to the maven release, somehow we
> have
> > > to point to the jar, but hard coding the version would be prone to
> error.
> > >
> > > Anyway, to answer your question, first of all I would just try to
> delete
> > > the old .jar, and see if that solves the problem.
> > >
> > > Regards,
> > > Norbert
> > >
> > > On Thu, Aug 30, 2018 at 9:01 AM Debraj Manna <subharaj.manna@gmail.com
> >
> > > wrote:
> > >
> > > > Cross-posting from stackoverflow
> > > > <
> > > >
> > >
> >
> https://stackoverflow.com/questions/52090357/how-to-upgrade-zookeeper-from-from-3-8-to-3-13
> > > > >
> > > >
> > > > I am trying to upgrade zookeeper from 3.4.8 to 3.4.13.
> > > >
> > > > Before upgrade the content of /usr/lib/zookeeper
> > > >
> > > > drwxr-xr-x 5 root root 4.0K Aug 23 08:39 . drwxr-xr-x 77 root root
> 12K
> > > Aug
> > > > 23 08:50 .. drwxr-xr-x 2 root root 4.0K Aug 23 08:39 bin lrwxrwxrwx 1
> > > root
> > > > root 19 May 24 11:25 conf -> /etc/zookeeper/conf drwxr-xr-x 2 root
> root
> > > > 4.0K Aug 23 08:39 lib -rw-r--r-- 1 root root 12K May 24 11:25
> > LICENSE.txt
> > > > -rw-r--r-- 1 root root 170 May 24 11:25 NOTICE.txt -rw-r--r-- 1 root
> > root
> > > > 1.3M Aug 23 08:39 zookeeper-3.4.8.jar lrwxrwxrwx 1 root root 38 Aug
> 23
> > > > 08:39 zookeeper.jar -> /usr/lib/zookeeper/zookeeper-3.4.8.jar
> > > >
> > > > As mentioned in answer <https://serverfault.com/a/758671/300869>
I
> > have
> > > > downloaded the zookeeper from this link
> > > > <
> > > >
> > >
> >
> http://mirrors.fibergrid.in/apache/zookeeper/zookeeper-3.4.13/zookeeper-3.4.13.tar.gz
> > > > >
> > > > and
> > > > placed the zookeeper-3.4.13.jar in /usr/lib/zookeeper and pointed the
> > > > symbolic link like below
> > > >
> > > > lrwxrwxrwx  1 root root   39 Aug 30 03:19 zookeeper.jar ->
> > > > /usr/lib/zookeeper/zookeeper-3.4.13.jar
> > > >
> > > > But on checking the status after resarting zookeeper it is still
> > pointing
> > > > to 3.4.8
> > > >
> > > > ubuntu@vrni-platform:/etc/zookeeper/conf$ telnet localhost 2181
> > > > Trying 127.0.0.1...
> > > > Connected to localhost.
> > > > Escape character is '^]'.
> > > > status
> > > > Zookeeper version: 3.4.8--1, built on 02/06/2016 03:18 GMT
> > > >
> > > > It appears this is because of the way the jars are loaded from
> > > > /usr/lib/zookeeper/bin/zkEnv.sh
> > > >
> > > > #release tarball format
> > > > for i in "$ZOOBINDIR"/../zookeeper-*.jar
> > > > do
> > > >   CLASSPATH="$i:$CLASSPATH"
> > > > done
> > > >
> > > > Can someone let me know is this some known issue is zkEnv.sh? Is this
> > > > expected?
> > > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message