[
https://issues.apache.org/jira/browse/KUDU-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644941#comment-17644941
]
ASF subversion and git services commented on KUDU-3403:
-------------------------------------------------------
Commit 7f7e2cf4611e9fb6fe07a57df8762f1ce2e71b8f in kudu's branch
refs/heads/master from Ashwani Raina
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=7f7e2cf46 ]
KUDU-3403 Enable kudu CLI to accept specific leader to step down
Accept UUID as an argument to identify the leader
and deduce other information like host, port, etc.
This can be useful in scenario when master is out of sync and
user wants to choose a specific leader to step down instead of
relying on information about leader in the tablet configuration
known to master.
Change-Id: I40569faa40a8173c51504c7567aa84a6ae1fb64a
Reviewed-on: http://gerrit.cloudera.org:8080/19024
Tested-by: Kudu Jenkins
Reviewed-by: Alexey Serbin <ale...@apache.org>
> 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)
