Ethan Rose created HDDS-8447:
--------------------------------
Summary: 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
Assignee: Ethan Rose
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]
