[jira] [Commented] (KUDU-3403) Add flag to accept current leader uuid that needs to step down

["shenxingwuying (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KUDU-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609127#comment-17609127 ] 

shenxingwuying commented on KUDU-3403:
--------------------------------------

As you said, maybe masters' leader and tservers' leader is not consistency. Adding a gflags for Kudu CLI may have some risk, because it need kudu administrators' judgement, they also input an error current leader uuid. Althought they can retry another one uuid, but why the kudu CLI do this?

 

So IMO, if kudu CLI get master' leader not the real one, kudu CLI can retry the next one voter maybe it is the real leader, if no, continue retry the next one(3 replication refactor is the last).

> Add flag to accept current leader uuid that needs to step down
> --------------------------------------------------------------
>
>                 Key: KUDU-3403
>                 URL: https://issues.apache.org/jira/browse/KUDU-3403
>             Project: Kudu
>          Issue Type: Improvement
>          Components: CLI
>            Reporter: Ashwani Raina
>            Assignee: Ashwani Raina
>            Priority: Minor
>
> Currently, Kudu tablet leader step down cli command does not provide a flag to explicitly mention current leader uuid.
> This bug is to track the changes to add such an option.
> The flag can be used in a case where master config is out of sync and instead of relying on leader information on master, user wants to input leader uuid explicitly and transfer the leadership from there to another node.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)