Re: Is zookeeper 3.4.13 client backward compatible with 3.4.8?

[Debraj Manna]

Thanks Tamaas for replying.

On Thu 30 Aug, 2018, 9:51 PM Tamas Penzes, 
wrote:

> Hi Debraj,
>
> ZooKeeper 3.4.13 is only 5 bugfix version above 3.4.8. They are from the
> same major.minor version, which means they must be compatible on API level
> (can work together).
>
> On the other hand 3.4.13 contains bugfixes which can have effects on server
> and client side too. If you use different version on server and client side
> you might run into problems which are fixed in 3.4.13 on server side but
> not yet in 3.4.8 in your clients. It can make harder to find the root cause
> of any issue.
>
> Regards, Tamaas
>
> On Thu, Aug 30, 2018 at 5:54 PM Debraj Manna 
> wrote:
>
> > Hi
> >
> > I have read about the backward compatability as mentioned in the
> confluence
> > page
> >  >.
> > But I am still having the below doubt can someone confirm
> >
> > I upgraded to zookeeper servers to 3.4.13 from 3.4.8. I want to upgrade
> > java client also to 3.4.13 from 3.4.8. Can someone let me if the
> zookeeper
> > clients are also backward compatible? I have few other dependencies which
> > are using zookeeper client 3.4.8. So confirming.
> >
> > After reading the above confluence page it appears yes but I want to
> > confirm.
> >
> > Thanks,
> >
>
>
> --
> *Tamás Pénzes* | Engineering Manager
> e. tam...@cloudera.com
> cloudera.com 
>
> [image: Cloudera] 
>
> [image: Cloudera on Twitter]  [image:
> Cloudera on Facebook]  [image: Cloudera
> on LinkedIn] 
> --
>

Re: Is zookeeper 3.4.13 client backward compatible with 3.4.8?

[Tamas Penzes]

Hi Debraj,

ZooKeeper 3.4.13 is only 5 bugfix version above 3.4.8. They are from the
same major.minor version, which means they must be compatible on API level
(can work together).

On the other hand 3.4.13 contains bugfixes which can have effects on server
and client side too. If you use different version on server and client side
you might run into problems which are fixed in 3.4.13 on server side but
not yet in 3.4.8 in your clients. It can make harder to find the root cause
of any issue.

Regards, Tamaas

On Thu, Aug 30, 2018 at 5:54 PM Debraj Manna 
wrote:

> Hi
>
> I have read about the backward compatability as mentioned in the confluence
> page
> .
> But I am still having the below doubt can someone confirm
>
> I upgraded to zookeeper servers to 3.4.13 from 3.4.8. I want to upgrade
> java client also to 3.4.13 from 3.4.8. Can someone let me if the zookeeper
> clients are also backward compatible? I have few other dependencies which
> are using zookeeper client 3.4.8. So confirming.
>
> After reading the above confluence page it appears yes but I want to
> confirm.
>
> Thanks,
>


-- 
*Tamás Pénzes* | Engineering Manager
e. tam...@cloudera.com
cloudera.com 

[image: Cloudera] 

[image: Cloudera on Twitter]  [image:
Cloudera on Facebook]  [image: Cloudera
on LinkedIn] 
--

Is zookeeper 3.4.13 client backward compatible with 3.4.8?

[Debraj Manna]

Hi

I have read about the backward compatability as mentioned in the confluence
page
.
But I am still having the below doubt can someone confirm

I upgraded to zookeeper servers to 3.4.13 from 3.4.8. I want to upgrade
java client also to 3.4.13 from 3.4.8. Can someone let me if the zookeeper
clients are also backward compatible? I have few other dependencies which
are using zookeeper client 3.4.8. So confirming.

After reading the above confluence page it appears yes but I want to
confirm.

Thanks,

Re: How to upgrade zookeeper from 3.4.8 to 3.4.13?

[Debraj Manna]

I have removed other zookeeper-.jar and it is working fine.

Thanks,

On Thu, Aug 30, 2018 at 3:48 PM Norbert Kalmar 
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 
> 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
> > 
> > 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  >
> > > 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  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?
> > > >
> > >
> >
>

Re: How to upgrade zookeeper from 3.4.8 to 3.4.13?

[Norbert Kalmar]

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 
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
> 
> 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 
> > 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  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?
> > >
> >
>

Re: How to upgrade zookeeper from 3.4.8 to 3.4.13?

[Debraj Manna]

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 
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 
> 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  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?
> >
>

Re: How to upgrade zookeeper from 3.4.8 to 3.4.13?

[Norbert Kalmar]

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 
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  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?
>

How to upgrade zookeeper from 3.4.8 to 3.4.13?

[Debraj Manna]

Cross-posting from stackoverflow


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  I have
downloaded the zookeeper from this link

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?