[
https://issues.apache.org/jira/browse/ZOOKEEPER-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14230963#comment-14230963
]
Hongchao Deng commented on ZOOKEEPER-2076:
------------------------------------------
Hi [~shralex].
Could you do me a favor for two things:
1. share how you measure the time so I can do the same?
2. I wonder if you comment out the line
https://github.com/apache/zookeeper/blob/trunk/src/java/main/org/apache/zookeeper/server/quorum/Leader.java#L418-418
and measure the time again. It takes a snapshot, writes it to *DISK* here.
After all, I wonder if there is a way to do a simpler election because we
already know they are synced.
> 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)
