[
https://issues.apache.org/jira/browse/HDDS-11839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18104790#comment-18104790
]
Dian-Xuan Yang commented on HDDS-11839:
---------------------------------------
Hello! I'd like to work on this.
Plan: resolve the {{--new-leader-id}} argument on the SCM side — try it as a
Raft peer id (UUID) first, and fall back to matching it against the configured
SCM node ids via their Ratis address, so {{ozone admin scm transfer}} accepts
the same node id form that {{ozone admin om transfer}} already does.
> Mismatch in leadership transfer node ID
> ---------------------------------------
>
> Key: HDDS-11839
> URL: https://issues.apache.org/jira/browse/HDDS-11839
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone CLI
> Reporter: Pyttel
> Priority: Major
> Labels: newbie
>
> Leadership transfer expects leader to be identified by UUID for SCM, but node
> ID for OM:
> {code}
> $ ozone admin scm transfer --new-leader-id scm1
> Target scm1 not found in group [891cd056-3cf1-4e52-9cac-eff0af7bfefe,
> b25f513f-ddf7-4382-a3f0-fe5b209a7a26, ac63c8ae-1f4c-4fa7-9eed-e279d0b573ff].
> $ ozone admin om transfer --new-leader-id om1
> Transfer leadership successfully to om1.
> {code}
> Ideally it should accept both kinds of ID.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
