You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Zameer Manji (JIRA)" <ji...@apache.org> on 2016/12/01 15:30:58 UTC
[jira] [Reopened] (AURORA-1669) Kill twitter/commons ZK libs when
Curator replacements are vetted
[ https://issues.apache.org/jira/browse/AURORA-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zameer Manji reopened AURORA-1669:
----------------------------------
Re-opening this because of AURORA-1840
Per [~jsirois]'s suggestion we may need to upgrade [Curator|https://issues.apache.org/jira/browse/AURORA-1840?focusedCommentId=15712226&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15712226].
> 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)