[
https://issues.apache.org/jira/browse/KUDU-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609439#comment-17609439
]
Ashwani Raina edited comment on KUDU-3403 at 9/26/22 12:08 PM:
---------------------------------------------------------------
Purpose of adding this flag is to enable user/admin to be able to transfer
leadership from current leader if master is out of sync.
Even though, this could be a rare scenario but it is possible and in such
situations, having an additional flag makes more sense that would provide
flexibility admin to choose the right current leader.
If we go choose retry approach, we would end up iterating through all the nodes
and keep issuing 'step down' for each until we reach actual leader,
and this would change the behavior of existing logic where we find the leader
from master and transferring leadership from it.
Changing this behavior may also require changing the test cases (if any) that
try create 'master out of sync' scenario and expect an error when 'step down'
is issued.
Having a separate flag to denote current leader would give admin option to
specify one, presumably the correct one most of the times.
Even if a wrong current leader is input, Kudu CLI throws the appropriate error.
was (Author: JIRAUSER293774):
Purpose of adding this flag is to enable user/admin to be able to transfer
leadership from current leader if master is out of sync.
Even though, this could be a rare scenario but it is possible and in such
situations, having an additional flag makes more sense that would provide
flexibility admin to choose the right current leader.
If we go choose retry approach, we would end up iterating through all the nodes
and keep issuing 'step down' for each until we reach actual leader,
and this would change the behavior of existing logic where we find the leader
from master and transferring leadership from it.
Changing this behavior may also be required changing the test cases (if any)
that try create 'master out of sync' scenario and expect an error when 'step
down' is issued.
Having a separate flag to denote current leader would give admin option to
specify one, presumably the correct one most of the times.
Even if a wrong current leader is input, Kudu CLI throws the appropriate error.
> 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)
