curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CURATOR-246) Support more stable leader election on unstable ZK connection
Date Fri, 21 Aug 2015 02:26:46 GMT

     [ https://issues.apache.org/jira/browse/CURATOR-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jordan Zimmerman updated CURATOR-246:
-------------------------------------

Was "Support more stable leader election on unstable ZK connection" - converted to a parent
task for a more general solution

> Support more stable leader election on unstable ZK connection
> -------------------------------------------------------------
>
>                 Key: CURATOR-246
>                 URL: https://issues.apache.org/jira/browse/CURATOR-246
>             Project: Apache Curator
>          Issue Type: New Feature
>          Components: Framework, Recipes
>            Reporter: Dong Lei
>
> Spark now leverage curator to help manage the connections to ZK and do leader election.

> Currently, whenever a ZK session gets disassociated, the ConnectionStateManager will
be aware and mark the state to be SUSPENDED and a new leader election will be triggered. 
> Even though a ZK session is able to reconnect to another machine very soon. 
> I wonder if we can tolerate such unstable network trembling and do not trigger a leader
election. Because the upper layer application's (like spark) reaction of new leader can be
very costly. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message