[
https://issues.apache.org/jira/browse/HDDS-6611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17928098#comment-17928098
]
Ethan Rose commented on HDDS-6611:
----------------------------------
Do we need a new container schema version? I think even for old containers
created before this change we will know the locations of the chunks and
metadata paths without needing to know which version they were created in. I
think we just need a datanode layout feature since old versions will look for
these paths on downgrade.
> Remove chunksPath and metadataPath from container yaml file
> -----------------------------------------------------------
>
> Key: HDDS-6611
> URL: https://issues.apache.org/jira/browse/HDDS-6611
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Datanode
> Reporter: Ethan Rose
> Assignee: Sammi Chen
> Priority: Major
>
> Currently the .container files of KeyValueContainers contain absolute paths
> to the chunks directory and metadata directory, which is used to find the
> container's contents after reading the container file. This means that if the
> mount points of volumes specified in hdds.datanode.dir configs change, the
> datanode will find the container files and try to load the containers, but
> report that the container is missing pieces because the container file's
> chunks and metadata directories no longer exist.
> This is somewhat inconsistent with other directory configurations, because it
> is the only one (as far as I know) where changing its value to a new location
> that has the same data will cause a failure.
> This task will remove the chunksPath and metadataPath from container yaml
> file, when container is moved around(replication, or mount point changes),
> container directory will still be self constructed, and there is no need to
> update the yaml file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
