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 2016/06/24 23:08:16 UTC

[jira] [Updated] (KUDU-1504) Add a tool to force a Raft config change

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

Mike Percy updated KUDU-1504:
-----------------------------
    Issue Type: New Feature  (was: Bug)

> Add a tool to force a Raft config change
> ----------------------------------------
>
>                 Key: KUDU-1504
>                 URL: https://issues.apache.org/jira/browse/KUDU-1504
>             Project: Kudu
>          Issue Type: New Feature
>          Components: consensus, ops-tooling
>    Affects Versions: 0.9.0
>            Reporter: Mike Percy
>
> It would be useful to implement a tool that allowed for an administrator-controlled "forced" configuration change. This type of thing is useful as a "parachute" if, for example, 2 nodes of a 3-node configuration were permanently offline. An administrator may wish to accept whatever potential data loss occurred and force the configuration to be composed of a single node so that it could come back online and then grown back to a larger configuration size again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)