You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/02/14 13:56:00 UTC
[jira] [Updated] (HDDS-12323) Improve container import failure cleanup flow
[ https://issues.apache.org/jira/browse/HDDS-12323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HDDS-12323:
----------------------------------
Labels: pull-request-available (was: )
> Improve container import failure cleanup flow
> ---------------------------------------------
>
> Key: HDDS-12323
> URL: https://issues.apache.org/jira/browse/HDDS-12323
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Sammi Chen
> Assignee: Sammi Chen
> Priority: Major
> Labels: pull-request-available
>
> When a schema V3 container failed to be imported, three resource will be cleaned up,
> a. the potential still existed downloaded *.tar file on volume's tmp/container-copy/ directory
> b. the imported container metadata in RocksDB
> c. the potential existed $containerID directory on data volume.
> Currently, the clean up order is a -> b -> c.
> Given that during Datanode startup, only a missing or incorrect container.yaml file will get the container be skip to be loaded by datanode, we should first make sure container.yaml file is inaccessible to datanode after the container import is failed.
> This task aims to change the clean up order to a -> c -> b.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org