Re: OK to use 3.6.1 (or 3.5.8) client against a 3.4.6 server?

2020-08-31 Thread Szalay-Bekő Máté
Hello!

I think if you don't use any new ZooKeeper feature, then it is safe to use
the 3.5.8 or 3.6.1 clients with the old (3.4.6) server. But as far as I
know, the other approach should work too: using 3.4.6 clients with 3.5.8
or 3.6.1 servers. I don't really know which way would be better for
ZooKeeper.

When we were planning our upgrade in 2019, we did some compatibility tests
with some small sample applications on a matrix of different server-client
combinations to actually make sure we won't have any problems, and found
back there no incompatibilities. (this tests were not executed yet on 3.5.8
and 3.6.1, but I expect the same results on the more recent versions)

Before your upgrade, make sure you check:
https://cwiki.apache.org/confluence/display/ZOOKEEPER/Upgrade+FAQ

Kind regards,
Mate


On Fri, Aug 28, 2020 at 10:31 PM  wrote:

> It should work either way but I would suggest to upgrade zookeeper server
> version 1st .
>
> On 8/28/20, 1:29 PM, "John Lindwall"  wrote:
>
> [External]
>
>
> We are considering upgrading our zookeeper servers from 3.4.6 to
> either 3.5.8 or 3.6.1.  I wonder if will work if we proactively upgrade our
> client versions from 3.4.6 to the new, more current version (3.5.8 or
> 3.6.1) and run that newer client code against the older 3.4.6 servers?
> Later when we update the servers, then the client version and the server
> versions will match.
> Obviously we will not make use of any new API methods added to
> zookeeper since 3.4.6; in fact we will simply be recompiling our existing
> client code against the new libs (which works as I just tested it).
> Thanks!
> -- John
>
>
> This e-mail and any files transmitted with it are for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information. If you are not the intended recipient(s), please reply to the
> sender and destroy all copies of the original message. Any unauthorized
> review, use, disclosure, dissemination, forwarding, printing or copying of
> this email, and/or any action taken in reliance on the contents of this
> e-mail is strictly prohibited and may be unlawful. Where permitted by
> applicable law, this e-mail and other e-mail communications sent to and
> from Cognizant e-mail addresses may be monitored.
> This e-mail and any files transmitted with it are for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information. If you are not the intended recipient(s), please reply to the
> sender and destroy all copies of the original message. Any unauthorized
> review, use, disclosure, dissemination, forwarding, printing or copying of
> this email, and/or any action taken in reliance on the contents of this
> e-mail is strictly prohibited and may be unlawful. Where permitted by
> applicable law, this e-mail and other e-mail communications sent to and
> from Cognizant e-mail addresses may be monitored.
>


Re: OK to use 3.6.1 (or 3.5.8) client against a 3.4.6 server?

2020-08-28 Thread Manoj.Agrawal2
It should work either way but I would suggest to upgrade zookeeper server 
version 1st .

On 8/28/20, 1:29 PM, "John Lindwall"  wrote:

[External]


We are considering upgrading our zookeeper servers from 3.4.6 to either 
3.5.8 or 3.6.1.  I wonder if will work if we proactively upgrade our client 
versions from 3.4.6 to the new, more current version (3.5.8 or 3.6.1) and run 
that newer client code against the older 3.4.6 servers?  Later when we update 
the servers, then the client version and the server versions will match.
Obviously we will not make use of any new API methods added to zookeeper 
since 3.4.6; in fact we will simply be recompiling our existing client code 
against the new libs (which works as I just tested it).
Thanks!
-- John


This e-mail and any files transmitted with it are for the sole use of the 
intended recipient(s) and may contain confidential and privileged information. 
If you are not the intended recipient(s), please reply to the sender and 
destroy all copies of the original message. Any unauthorized review, use, 
disclosure, dissemination, forwarding, printing or copying of this email, 
and/or any action taken in reliance on the contents of this e-mail is strictly 
prohibited and may be unlawful. Where permitted by applicable law, this e-mail 
and other e-mail communications sent to and from Cognizant e-mail addresses may 
be monitored.
This e-mail and any files transmitted with it are for the sole use of the 
intended recipient(s) and may contain confidential and privileged information. 
If you are not the intended recipient(s), please reply to the sender and 
destroy all copies of the original message. Any unauthorized review, use, 
disclosure, dissemination, forwarding, printing or copying of this email, 
and/or any action taken in reliance on the contents of this e-mail is strictly 
prohibited and may be unlawful. Where permitted by applicable law, this e-mail 
and other e-mail communications sent to and from Cognizant e-mail addresses may 
be monitored.