[HDDS-6749] SCM includes itself as peer in addSCM request

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.3.0
• Component/s: SCM HA
• Labels: pull-request-available
• Target Version/s: 1.3.0, 1.2.2
• Assignee: Attila Doroszlai
• Reporter: Attila Doroszlai
• Created: 13/May/22 22:12
• Updated: 11/Jul/23 09:17
• Resolved: 17/May/22 06:03

Description

SCM during start sends addSCM request to its peers. It tries to exclude itself from the target list:

https://github.com/apache/ozone/blob/40461504478182af509db7098d4e173011d27e5a/hadoop-hdds/framework/src/main/java/org/apache/hadoop/hdds/utils/HAUtils.java#L119-L121

    OzoneConfiguration config = SCMHAUtils.removeSelfId(conf, selfId);
    try {
      return getScmBlockClient(config).addSCM(request);

but removeSelfId does not work.

Issue Links

• fixes: HDDS-6442 SCM HA on Kubernetes failed
• links to: GitHub Pull Request #3413