[
https://issues.apache.org/jira/browse/KUDU-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-1721.
-------------------------------
Resolution: Fixed
Assignee: Dinesh Bhat (was: zhangsong)
Fix Version/s: 1.4.0
> 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
> Assignee: Dinesh Bhat
> Priority: Major
> Fix For: 1.4.0
>
>
> 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
(v7.6.3#76005)
