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

Posted to issues@kudu.apache.org by "Will Berkeley (JIRA)" <ji...@apache.org> on 2018/10/18 00:47:00 UTC

[jira] [Resolved] (KUDU-2245) Leadership transfer (graceful step down)

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

Will Berkeley resolved KUDU-2245.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.0

Added in e61de497c487f33fe1a99c9df6dfb697e8efb757.

> Leadership transfer (graceful step down)
> ----------------------------------------
>
>                 Key: KUDU-2245
>                 URL: https://issues.apache.org/jira/browse/KUDU-2245
>             Project: Kudu
>          Issue Type: Improvement
>          Components: consensus
>            Reporter: Mike Percy
>            Assignee: Will Berkeley
>            Priority: Major
>             Fix For: 1.9.0
>
>
> Leadership transfer, also referred to as graceful leader step down, is a concept from the Raft dissertation (Section 3.10: Leadership transfer extension) where a leader can select a replica to "take over" as leader, and gracefully transfer leadership to that node by engineering an election in which that node is highly likely to win. This minimizes the period in a leadership change during which there is no recognized leader, and therefore minimizes latency spikes during a leader change.
> This feature can be useful when the leader replica should be removed from the tablet configuration. This can happen when the tablet server running the leader replica is being decommissioned, or in the case of tablet replica rebalancing where the tablet server hosting the leader replica can be considered overloaded.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)