[
https://issues.apache.org/jira/browse/ZOOKEEPER-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14230747#comment-14230747
]
Alexander Shraer commented on ZOOKEEPER-2076:
---------------------------------------------
I don't have a clear idea of what's needed for part 1. But when I measured the
latency of the leader handoff it still took about 1 second, even though it
should be pretty much immediate. I think this can be improved. The idea of part
1 here is to see where this time is spent and improve if possible.
> 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
>
> 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.4#6332)
