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

Zameer Manji commented on AURORA-1669:
--------------------------------------

For #2 we could probably have the leader write out the {{member_}} node as a 
{{PersistentNode}}. This would be backwards compatible and we would be 
resilient to session timeouts.

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

Reply via email to