[
https://issues.apache.org/jira/browse/HDDS-6611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ethan Rose updated HDDS-6611:
-----------------------------
Description:
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.
was: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.
> Support changing names of hdds.datanode.dir directories
> -------------------------------------------------------
>
> Key: HDDS-6611
> URL: https://issues.apache.org/jira/browse/HDDS-6611
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Datanode
> Reporter: Ethan Rose
> 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 message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
