[
https://issues.apache.org/jira/browse/AURORA-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712330#comment-15712330
]
Zameer Manji commented on AURORA-1669:
--------------------------------------
Here is my assessment on how to fix AURORA-1840:
* We cannot upgrade to Curator 3.x because it will only work with ZK 3.5.x
which has not been released yet.
* We can move to the {{LeaderSelector}} recipe (per [~StephanErb]'s suggestion)
and figure out how to make it backwards compatible for leader discovery.
* We can figure out how to override the error handling capability of
{{LeaderLatch}} to have it not lose leadership on session suspension, only
loss.
> Kill twitter/commons ZK libs when Curator replacements are vetted
> -----------------------------------------------------------------
>
> Key: AURORA-1669
> URL: https://issues.apache.org/jira/browse/AURORA-1669
> Project: Aurora
> Issue Type: Task
> Reporter: John Sirois
> Assignee: John Sirois
>
> Once we have reports from production users that the Curator zk plumbing
> introduced in AURORA-1468 is working well, the {{-zk_use_curator}} flag
> should be deprecated and then the flag and commons code killed. If the
> vetting happens before the next release ({{0.14.0}}), we can dispense with a
> deprecation cycle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
