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

Posted to issues@kudu.apache.org by "Andrew Wong (JIRA)" <ji...@apache.org> on 2019/08/12 21:40: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=16905605#comment-16905605 ] 

Andrew Wong commented on KUDU-1827:
-----------------------------------

A "decommissioning" state would be similar to "maintenance mode" because in both states, the tablet server should not be considered for the placement of new replicas.

Unlike maintenance mode, it should be valid (perhaps even encouraged, a la KUDU-2914) to move tablet replicas away from a tablet server that is being decommissioned.

> 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
>            Priority: Major
>              Labels: roadmap-candidate
>
> 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
(v7.6.14#76016)