[
https://issues.apache.org/jira/browse/HDDS-14365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krishna Kumar Asawa reassigned HDDS-14365:
------------------------------------------
Assignee: Priyesh K
> Redundant per volume VERSION file of Datanode
> ---------------------------------------------
>
> Key: HDDS-14365
> URL: https://issues.apache.org/jira/browse/HDDS-14365
> Project: Apache Ozone
> Issue Type: Improvement
> Environment: bq.
> Reporter: Sammi Chen
> Assignee: Priyesh K
> Priority: Major
>
> there are two VERSION files on each DN
> bash-5.1$ cat /data/hdds/hdds/VERSION
> #Mon Dec 29 07:12:04 UTC 2025
> datanodeUuid=1e9cbb46-38d1-4264-8ad9-e6c2ac6ec22a
> ctime=1766992324612
> clusterID=CID-73560f72-8f7e-424f-92d8-c3b0c28028c4
> layOutVersion=1
> storageID=DS-cc83ad9b-1b8e-4798-a09a-9dc31be51e0a
> bash-5.1$ cat /data/metadata/dnlayoutversion/VERSION
> #Mon Dec 29 07:12:04 UTC 2025
> cTime=1766992310921
> clusterID=CID-73560f72-8f7e-424f-92d8-c3b0c28028c4
> nodeType=DATANODE
> layoutVersion=10
> Per [~erose]'s info,
> There is one VERSION file per volume, and one global one for the whole
> datanode. Originally there was only one per volume, and later we needed one
> for the whole node so we added it to the metadata directory. You can ignore
> the layOutVersion field in the volume VERSION files. That was added in a very
> early version of Ozone as a hypothetical/speculative way to handle upgrades
> before the feature was even developed and never got used.
> This task aims to investigate whether the per volume VERSION can be removed
> completely without introduce any backward compatibility issue. And if
> feasible, implement it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
