[
https://issues.apache.org/jira/browse/OOZIE-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417922#comment-15417922
]
Robert Kanter commented on OOZIE-2231:
--------------------------------------
Oh, I didn't realize that requires ZooKeeper 3.5.x. They seem to only have the
newest Javadocs on their website, which is for the 3.x line.
According to the Curator website
{quote}
Curator 2.x.x - compatible with both ZooKeeper 3.4.x and ZooKeeper 3.5.x
Curator 3.x.x - compatible only with ZooKeeper 3.5.x and includes support for
new features such as dynamic reconfiguration, etc.
{quote}
2.11.0 should work with ZooKeeper 3.4.x.
I guess what we should do here is use Curator 2.11.0 with the ChildReaper for
now. And revisit if we want to upgrade to Curator 3.x for Oozie 5 without
ChildReaper (can you create another JIRA?).
CDH 5 is currently using ZooKeeper 3.4.5 (plus some patches). I'm not sure
what the plan is for CDH 6.
> Upgrade curator to latest version 2.8.0
> ---------------------------------------
>
> Key: OOZIE-2231
> URL: https://issues.apache.org/jira/browse/OOZIE-2231
> Project: Oozie
> Issue Type: Bug
> Components: HA
> Reporter: Purshotam Shah
> Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2231-00.patch, OOZIE-2231-01.patch
>
>
> It have some fix related to InterProcessReadWriteLock, ChildReaper,
> LeaderSelector which we use.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
