[ https://issues.apache.org/jira/browse/HDDS-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17177005#comment-17177005 ]
Marton Elek commented on HDDS-4107: ----------------------------------- cc [~avijayan] who is working on the upgrade design > replace scmID with clusterID for container and volume at Datanode side > ---------------------------------------------------------------------- > > Key: HDDS-4107 > URL: https://issues.apache.org/jira/browse/HDDS-4107 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task > Components: SCM > Reporter: Glen Geng > Assignee: Glen Geng > Priority: Major > Labels: backward-incompatible, pull-request-available, upgrade > > The disk layout per volume is as follows: > {code:java} > ../hdds/VERSION > ../hdds/<<scmUuid>>/current/<<containerDir>>/<<containerID>>/metadata > ../hdds/<<scmUuid>>/current/<<containerDir>>/<<containerID>>/<<dataDir>>{code} > However, after SCM-HA is enabled, a typical SCM group will consists of 3 > SCMs, each of the SCMs has its own scmUuid, meanwhile share the same > clusterID. > Since federation is not supported yet, only one cluster is supported now, > this Jira will change scmID to clusterID for container and volume at Datanode > side. > The disk layout after the change will be as follows: > {code:java} > ../hdds/VERSION > ../hdds/<<clusterID>>/current/<<containerDir>>/<<containerID>>/metadata > ../hdds/<<clusterID>>/current/<<containerDir>>/<<containerID>>/<<dataDir>>{code} -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org