[
https://issues.apache.org/jira/browse/HDDS-6611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524562#comment-17524562
]
Ethan Rose commented on HDDS-6611:
----------------------------------
Two possible solutions come to mind:
1. On startup, rewrite the container files to use relative paths for the chunks
and metadata directories. Code around container creation and import may need to
be changed as well to use relative paths.
2. On startup, rewrite the container files to use absolute paths for the chunks
and metadata directories, but update the paths to reflect the container's
current location. Code around container creation and import can remain
unchanged.
> 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 message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
