You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ivan Andika (Jira)" <ji...@apache.org> on 2026/10/21 07:23:00 UTC
[jira] [Resolved] (HDDS-17131) MiniOzoneHAClusterImpl#transferOMLeadershipToAnotherNode removes the old leader from the cluster's OM list
[ https://issues.apache.org/jira/browse/HDDS-17131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Andika resolved HDDS-17131.
--------------------------------
Fix Version/s: 2.3.0
Resolution: Fixed
> MiniOzoneHAClusterImpl#transferOMLeadershipToAnotherNode removes the old leader from the cluster's OM list
> ----------------------------------------------------------------------------------------------------------
>
> Key: HDDS-17131
> URL: https://issues.apache.org/jira/browse/HDDS-17131
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: test
> Reporter: Siyao Meng
> Assignee: Andy Huang
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.3.0
>
>
> {{transferOMLeadershipToAnotherNode}} does {{List<OzoneManager> omList = getOzoneManagersList(); omList.remove(currentLeader);}}. {{getOzoneManagersList()}} returns the backing list of {{MiniOzoneHAService}}, so the old leader is removed from the cluster: it no longer appears in {{getOzoneManagersList()}}, {{getOzoneManager(int)}} indexes shift, and {{stop()}} does not stop it. The target is also {{omList.get(0)}}, which may be a stopped OM.
> Used by TestOMHALeaderSpecificACLEnforcement and TestOzoneManagerHAFollowerReadWithAllRunning.
> *Fix:* copy the list and pick a running OM other than the current leader.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org