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

Posted to issues@kudu.apache.org by "Mike Percy (JIRA)" <ji...@apache.org> on 2017/12/20 00:27:00 UTC

[jira] [Commented] (KUDU-1827) Add capability and tool to gracefully decommission a tablet server

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

Mike Percy commented on KUDU-1827:
----------------------------------

If we want to decommission a tablet server hosting a leader replica, support for leadership transfer (graceful step down) would be very useful to reliably remove the given replica from the Raft configuration, since our current leader step-down implementation can cause write latency spikes, plus the likelihood of the previous leader becoming the leader again is high.

We do not allow a leader to evict itself from the config, so a leader must step down before it can be evicted by a new leader.

> Add capability and tool to gracefully decommission a tablet server
> ------------------------------------------------------------------
>
>                 Key: KUDU-1827
>                 URL: https://issues.apache.org/jira/browse/KUDU-1827
>             Project: Kudu
>          Issue Type: New Feature
>          Components: consensus, ops-tooling, tablet
>            Reporter: Mike Percy
>
> It would be useful to be able to decommission a tablet server gracefully, by taking it out of the candidate for getting new tablets and re-replicating its data to other servers before taking it out of tablet Raft configurations and shutting it down.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)