[
https://issues.apache.org/jira/browse/HADOOP-16763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16997453#comment-16997453
]
Wei-Chiu Chuang commented on HADOOP-16763:
------------------------------------------
[~nkalmar],
https://issues.apache.org/jira/browse/HADOOP-16579?focusedCommentId=16945744&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16945744
bq. Quick analysis: the ZK test failing creates a TestingServer which is
implemented in Curator. Curator supposedly decides based on ZK version on the
classpath if it runs in 3.5 or 3.4 mode. Somehow it looks like it decides to
run in 3.5 mode even though there is a 3.4 ZK on the classpath (that's why ZK
is excluded in curator's dependency).
For reason we didn't figure out, Curator decided to run in 3.5 mode. To get it
going we updated ZK on 3.5 too.
That is to say if we create a ZK 3.4 profile, it would also change Curator
version. That is fine if compatibility is preserved.
> Make Curator 4 run in soft-compatibility mode with ZooKeeper 3.4
> ----------------------------------------------------------------
>
> Key: HADOOP-16763
> URL: https://issues.apache.org/jira/browse/HADOOP-16763
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Íñigo Goiri
> Priority: Major
>
> HADOOP-16579 changed Curator to 4.2 and ZooKeeper to 3.5.
> This change relate to the client libraries used by the components.
> However, the ensemble in most deployments is 3.4 (default in Ubuntu for
> example).
> To allow this mode, there is a soft-compatibility mode described in
> http://curator.apache.org/zk-compatibility.html
> We should enable this soft-compatibility mode.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
