Ethan Rose created HDDS-5560:
--------------------------------
Summary: Datanodes' dnlayoutversion/VERSION file containers
incorrect cluster ID
Key: HDDS-5560
URL: https://issues.apache.org/jira/browse/HDDS-5560
Project: Apache Ozone
Issue Type: Sub-task
Reporter: Ethan Rose
**Taken from a datanode as part of a docker cluster
**Global version file at metadata/dnlayoutversion/VERSION (incorrect cluster
ID):
{code}
#Fri Jul 23 17:52:54 UTC 2021
firstUpgradeActionLayoutVersion=2
cTime=1627062428170
clusterID=18539b4c-28ae-4dfb-a668-6437c2df56f6
nodeType=DATANODE
layoutVersion=2
{code}
Volume specific version file at hdds/hdds/VERSION (correct):
{code}
#Fri Jul 23 17:45:20 UTC 2021
datanodeUuid=18539b4c-28ae-4dfb-a668-6437c2df56f6
ctime=1627062320832
clusterID=CID-faab32bd-91e1-4ffc-a942-e4252d8af722
layOutVersion=1
storageID=DS-1876fa77-6c75-4b91-b724-7802a362af52
{code}
Global datanode.id file (correct):
{code}
!!org.apache.hadoop.ozone.container.common.helpers.DatanodeIdYaml$DatanodeDetailsYaml
{
certSerialId: null,
currentVersion: 1,
hostName: b08914e5c4ae,
initialVersion: 1,
ipAddress: 10.9.0.15,
persistedOpState: IN_SERVICE,
persistedOpStateExpiryEpochSec: 0,
portDetails: {
},
uuid: 18539b4c-28ae-4dfb-a668-6437c2df56f6
}
{code}
All datanodes use the same cluster ID in their volume specific version files,
and SCM shows a matching cluster ID. This means the value
\{code}CID-faab32bd-91e1-4ffc-a942-e4252d8af722\{code} is the correct cluster
ID. The other two files show the datanode UUID as
\{code}18539b4c-28ae-4dfb-a668-6437c2df56f6\{code}, which is incorrectly used
as the cluster ID in the global datanode version file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
