zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Shraer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2076) Improve Leader Change Mechanism
Date Fri, 31 Mar 2017 17:46:41 GMT

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

Alexander Shraer commented on ZOOKEEPER-2076:
---------------------------------------------

Sure, [~atris], thanks for taking this on. BTW, perhaps both items in the description are
too much for a single JIRA, we could tackle one of them here and leave the other one for different
JIRA(s).

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

Mime
View raw message