aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Sirois (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1669) Kill twitter/commons ZK libs when Curator replacements are vetted
Date Wed, 15 Jun 2016 16:55:09 GMT

    [ https://issues.apache.org/jira/browse/AURORA-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15332078#comment-15332078
] 

John Sirois commented on AURORA-1669:
-------------------------------------

Noting that {{0.14.0}} has shipped so a deprecation cycle is needed. It's been pointed out
that the cycle should also flip the flag default to {{true}}; ie folks will need to specify
{{-no_zk_use_curator}} If they want to upgrade to {{0.15.0}} w/o the new Curator support.

> 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)

Mime
View raw message