[jira] [Commented] (HDDS-8447) Datanodes should not process container deletes for failed volumes

["Attila Doroszlai (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HDDS-8447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17720491#comment-17720491 ] 

Attila Doroszlai commented on HDDS-8447:
----------------------------------------

If datanode does not process delete container command for failed volume, will it not be retried?  Shouldn't it remove the container from in-memory state, while leaving the container contents on the disk?

> 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: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org