[
https://issues.apache.org/jira/browse/HDDS-8447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17722949#comment-17722949
]
Ethan Rose commented on HDDS-8447:
----------------------------------
Yes I should clarify the cleanup of in-memory vs. disk for the different
scenarios:
h3. Container delete fails because volume has failed
Currently the container will be unhealthy in the DN's memory. If a delete
command is received for this container, it should be removed from memory, but
not from the volume because the volume is failed. After HDDS-8448 We may not
move the container to unhealthy, and instead just clear out the in memory
entries once the volume fails.
h3. Container delete fails but volume has not failed.
This is the case that should be retried as you mentioned. The container should
not be removed from memory until it is successfully moved to the delete
directory. If delete is repeatedly failing, doing an on-demand volume scan on
failure can help prevent retrying forever on a volume that has gone bad.
> Datanodes should not process container deletes for failed volumes
> -----------------------------------------------------------------
>
> Key: HDDS-8447
> URL: https://issues.apache.org/jira/browse/HDDS-8447
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Datanode
> Reporter: Arun Sarin
> Priority: Major
>
> Before HDDS-6449, if there was an error deleting containers from datanodes,
> the operation would be abandoned, leaving behind container pieces which could
> be problematic on restart. After that fix, deletion is more robust and moves
> the container to a volume specific tmp directory before deletion. This
> requires the volume to be present and healthy otherwise it will fail and the
> DN will be stuck in a container delete retry loop. In this jira, we will:
> 1. Check if the volume is in the failed volume set before deleting a
> container.
> 2. Trigger an on-demand volume scan if there is an IO error deleting the
> container.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
