You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Glen Geng (Jira)" <ji...@apache.org> on 2020/12/02 07:53:00 UTC
[jira] [Updated] (HDDS-4538) SCM HA needs take care of the
generation of clusterID and scmUuid
[ https://issues.apache.org/jira/browse/HDDS-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Glen Geng updated HDDS-4538:
----------------------------
Description:
During the initialization of SCM, it will generate a random clusterID and scmUuid.
On Datanode, 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}
The metadata file for a typical container is as follows:
{code:java}
[ozoneadmin@tdw-9-179-144-104 /data6/hdds/hdds/326a5fe1-e63c-44b6-a57e-2f858fe4eaa7/current/containerDir0/262574/metadata]$ cat 262574.container
!<KeyValueContainerData>
checksum: f1473bc5a9f9fa307edf2040edf0fb5ac40912a5bd8610e2d42fa26693cc4b8f
chunksPath: /data6/hdds/hdds/326a5fe1-e63c-44b6-a57e-2f858fe4eaa7/current/containerDir0/262574/chunks
containerDBType: RocksDB
containerID: 262574
containerType: KeyValueContainer
layOutVersion: 2
maxSize: 5368709120
metadata: {}
metadataPath: /data6/hdds/hdds/326a5fe1-e63c-44b6-a57e-2f858fe4eaa7/current/containerDir0/262574/metadata
originNodeId: 26395209-1233-439a-9020-0ad8d6a8248e
originPipelineId: cf7bd510-ff60-4d35-9746-7463d30e13af
state: CLOSED
{code}
A typical SCM group consists of 3 SCMs, each of the them has its own scmUuid and clusterID, which will cause chaos in Datanode side.
For now, we just hard code the clusterID and scmUuid on HDDS-2823, so that we can setup a SCM raft group.
We need figure out a decent solution when merging back HDDS-2823 back to master.
> SCM HA needs take care of the generation of clusterID and scmUuid
> -----------------------------------------------------------------
>
> Key: HDDS-4538
> URL: https://issues.apache.org/jira/browse/HDDS-4538
> Project: Hadoop Distributed Data Store
> Issue Type: Task
> Components: SCM HA
> Affects Versions: 1.1.0
> Reporter: Glen Geng
> Priority: Major
>
> During the initialization of SCM, it will generate a random clusterID and scmUuid.
>
> On Datanode, 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}
> The metadata file for a typical container is as follows:
> {code:java}
> [ozoneadmin@tdw-9-179-144-104 /data6/hdds/hdds/326a5fe1-e63c-44b6-a57e-2f858fe4eaa7/current/containerDir0/262574/metadata]$ cat 262574.container
> !<KeyValueContainerData>
> checksum: f1473bc5a9f9fa307edf2040edf0fb5ac40912a5bd8610e2d42fa26693cc4b8f
> chunksPath: /data6/hdds/hdds/326a5fe1-e63c-44b6-a57e-2f858fe4eaa7/current/containerDir0/262574/chunks
> containerDBType: RocksDB
> containerID: 262574
> containerType: KeyValueContainer
> layOutVersion: 2
> maxSize: 5368709120
> metadata: {}
> metadataPath: /data6/hdds/hdds/326a5fe1-e63c-44b6-a57e-2f858fe4eaa7/current/containerDir0/262574/metadata
> originNodeId: 26395209-1233-439a-9020-0ad8d6a8248e
> originPipelineId: cf7bd510-ff60-4d35-9746-7463d30e13af
> state: CLOSED
> {code}
>
> A typical SCM group consists of 3 SCMs, each of the them has its own scmUuid and clusterID, which will cause chaos in Datanode side.
>
> For now, we just hard code the clusterID and scmUuid on HDDS-2823, so that we can setup a SCM raft group.
> We need figure out a decent solution when merging back HDDS-2823 back to master.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org