> On Dec. 29, 2015, 12:37 p.m., Stephan Erb wrote:
> > Looks like the 3.4 client also requires a 3.4 ZK server [1]. So, would it 
> > be possible to get a deprecation cycle for that change (i.e., announce in 
> > 0.12 and bump in 0.13)?
> > 
> > Unfortunately, we are still running our masters on ancient Debian Wheezy 
> > [2] and I suppose we are not the only one.
> > 
> > [1] 
> > http://zookeeper-user.578899.n2.nabble.com/Zookeeper-backward-compatibility-td7578798.html
> > [2] https://packages.debian.org/search?keywords=zookeeper
> 
> John Sirois wrote:
>     My understanding was that 3.4.x clients could operate against 3.3.x 
> servers as long as they avoided the new apis (multi).
>     
>     I just downloaded the 3.3.6 and 3.4.7 tarballs, started a local server 
> using 3.3.6 (`ln -s $PWD/conf/zoo_sample.cfg conf/zoo.cfg && 
> ./bin/zkServer.sh start-foreground`), connected using the 3.3.6 client 
> (`./bin/zkCli.sh`) and added some nodes and acl'd them in the digest scheme, 
> then connected using the 3.4.7 client, authed and read those nodes, modified 
> one, added a new one, and went back and read the new and modded with the 
> 3.3.6 client.  All was fine, but this was also a relatively simple setup.
> 
> Bill Farner wrote:
>     | So, would it be possible to get a deprecation cycle for that change 
> (i.e., announce in 0.12 and bump in 0.13)?
>     
>     Exploring the policy choice here - is there much upside to the 
> deprecation period over declaring "0.12 requires ZooKeeper >=3.4.x"?  Just 
> thinking out loud, since it's all communication and there's no step in which 
> we will be providing a compatibility bridge IIUC.
> 
> Stephan Erb wrote:
>     Good point actually. Given that even zookeeper 3.4 has been released 
> quite some time ago that would actually be fair as well.

what John said - everything but multi should work fine from the java 3.4 client 
libs connecting to a 3.3 server (i went through the changelog and couldn't see 
anything that would cause breakage).


- Raul


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/41762/#review112163
-----------------------------------------------------------


On Jan. 4, 2016, 4:55 a.m., Bill Farner wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41762/
> -----------------------------------------------------------
> 
> (Updated Jan. 4, 2016, 4:55 a.m.)
> 
> 
> Review request for Aurora, John Sirois and Zameer Manji.
> 
> 
> Repository: aurora
> 
> 
> Description
> -------
> 
> Primary motivation here is to get past 3.4.0, which changed how logging works 
> in ZK (primarily via slf4j).  This will make it easier to have a cohesive 
> logging story.
> 
> There was some fallout - I did not update to latest - 3.4.7.  I encountered 
> issues with a kerberos-related test (see comment in `build.gradle`) with 
> >=3.4.3.  I spent a few minutes looking for a solution, but decided to stop 
> short so as to return to the work i was really trying to tackle.
> 
> 
> Diffs
> -----
> 
>   NEWS 965fbf41d11296b08cdc722cfece9e37e49dbb6e 
>   build.gradle 6f89958c3845f01830f792cc78a755542b41e162 
>   
> commons/src/main/java/org/apache/aurora/common/zookeeper/testing/ZooKeeperTestServer.java
>  03d47c37f67dee64eca2107ab1510c7efcdd0931 
> 
> Diff: https://reviews.apache.org/r/41762/diff/
> 
> 
> Testing
> -------
> 
> end-to-end tests
> 
> 
> Thanks,
> 
> Bill Farner
> 
>

Reply via email to