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

Posted to issues@kudu.apache.org by "Grant Henke (Jira)" <ji...@apache.org> on 2020/06/02 13:07:00 UTC

[jira] [Resolved] (KUDU-1720) Expose ability to appoint a replica as leader via RPC

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

Grant Henke resolved KUDU-1720.
-------------------------------
    Fix Version/s: NA
       Resolution: Fixed

> Expose ability to appoint a replica as leader via RPC
> -----------------------------------------------------
>
>                 Key: KUDU-1720
>                 URL: https://issues.apache.org/jira/browse/KUDU-1720
>             Project: Kudu
>          Issue Type: Bug
>          Components: consensus
>            Reporter: Mike Percy
>            Priority: Major
>             Fix For: NA
>
>
> Today we have an internal API call in RaftConsensus called EmulateElection() that causes a node to increment its term and begin acting as Raft leader without initiating an election. Exposing this would allow us to use this in emergency scenarios, where all replicas except one are offline and we need to force a node to become leader in order to then force an unsafe configuration change to be serialized to the WAL.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)