You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Flavio Junqueira (JIRA)" <ji...@apache.org> on 2017/03/31 11:44:41 UTC

[jira] [Assigned] (ZOOKEEPER-2076) Improve Leader Change Mechanism

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

Flavio Junqueira reassigned ZOOKEEPER-2076:
-------------------------------------------

    Assignee: Atri Sharma

> Improve Leader Change Mechanism
> -------------------------------
>
>                 Key: ZOOKEEPER-2076
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2076
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.5.0
>            Reporter: Alexander Shraer
>            Assignee: Atri Sharma
>
> When a leader is removed during a reconfiguration, ZOOKEEPER-107 uses a mechanism where the old leader nominates the new one. Although it reduces the time for a new leader to be elected, it still takes too long. This JIRA is for two things:
> 1. Improve the mechanism, e.g., avoid loading snapshots, etc. during the handoff.
> 2. Make it a first-class citizen & export it as a client API. We get questions about this once in a while - how do I cause a different leader to be elected ? Currently the response is either kill or reconfigure the current leader.
> Any one interested to work on this ?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)