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

Posted to issues@kudu.apache.org by "zhangsong (JIRA)" <ji...@apache.org> on 2016/12/02 07:28:58 UTC

[jira] [Assigned] (KUDU-1721) Expose ability to force an unsafe Raft configuration change

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

zhangsong reassigned KUDU-1721:
-------------------------------

    Assignee: zhangsong

> 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: zhangsong
>
> 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)