[
https://issues.apache.org/jira/browse/HDDS-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4107:
----------------------------
Description:
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 enabled, a typical SCM group consists of 3 SCMs, each SCM
has its own scmUuid, meanwhile share the same clusterID.
Since federation is not supported yet, this Jira will change scmID to clusterID
for container and volume, the disk layout will as follows:
{code:java}
../hdds/VERSION
../hdds/<<clusterID>>/current/<<containerDir>>/<<containerID>>/metadata
../hdds/<<clusterID>>/current/<<containerDir>>/<<containerID>>/<<dataDir>>{code}
was:
The disk layout per volume is as follows:
../hdds/VERSION
../hdds/<<scmUuid>>/current/<<containerDir>>/<<containerID>>/metadata
../hdds/<<scmUuid>>/current/<<containerDir>>/<<containerID>>/<<dataDir>>
However, after SCM-HA enabled, a typical SCM group consists of 3 SCMs, each SCM
has its own scmUuid, meanwhile share the same clusterID.
Since federation is not supported yet, this Jira will change scmID to clusterID
for container and volume, the disk layout will as follows:
../hdds/VERSION
../hdds/<<clusterID>>/current/<<containerDir>>/<<containerID>>/metadata
../hdds/<<clusterID>>/current/<<containerDir>>/<<containerID>>/<<dataDir>>
> 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
>
> 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 enabled, a typical SCM group consists of 3 SCMs, each
> SCM has its own scmUuid, meanwhile share the same clusterID.
> Since federation is not supported yet, this Jira will change scmID to
> clusterID for container and volume, the disk layout will 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
