[
https://issues.apache.org/jira/browse/KUDU-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816812#comment-15816812
]
Mike Percy commented on KUDU-1504:
----------------------------------
Hmm I suppose you are right -- this could be duped with KUDU-1330. Sorry about
that.
Regarding KUDU-1721 I think it encompasses the core consensus / API work to
allow for forcing an unsafe config change and testing it while this JIRA and
KUDU-1330 encompass exposing that functionality as an administrator-facing tool.
> 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)
