[
https://issues.apache.org/jira/browse/KUDU-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602119#comment-15602119
]
Mike Percy commented on KUDU-1721:
----------------------------------
I think this represents an approach and KUDU-1504 represents a tool that can
use this approach to accomplish something. So I'll mark this as blocking that
one.
> Expose ability to force an unsafe Raft configuration change
> -----------------------------------------------------------
>
> Key: KUDU-1721
> URL: https://issues.apache.org/jira/browse/KUDU-1721
> Project: Kudu
> Issue Type: Bug
> Components: consensus
> Reporter: Mike Percy
>
> Add the ability to force an “unsafe” configuration change via RPC to the
> leader. Instead of specifying AddServer() or RemoveServer(), which enforce
> one-by-one configuration changes due to their inherent contract, we could
> specify an unsafe configuration change API for administrative / emergency
> cases only that the leader would process without going through the normal
> "one by one" safety checks required by the Raft dissertation config change
> protocol.
> The leader should still reject configuration changes in which is it not a
> member of the requested new configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
