You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2023/01/05 23:45:00 UTC

[jira] [Commented] (HDDS-7732) EC: Verify block deletion from "missing" EC containers

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

Ethan Rose commented on HDDS-7732:
----------------------------------

If the container is deleted, there may still be block delete commands for it in SCM's deleted block log that are not removed since the required number of datanodes have not acknowledged the delete. A solution like HDDS-7126 could fix this.

> EC: Verify block deletion from "missing" EC containers
> ------------------------------------------------------
>
>                 Key: HDDS-7732
>                 URL: https://issues.apache.org/jira/browse/HDDS-7732
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Ethan Rose
>            Priority: Major
>
> In EC, a container is considered "missing" if there are not enough replicas to reconstruct it. If a key is deleted from one of these containers, the blocks should still be deleted from the replicas that are present. When all the blocks are deleted, the remaining replicas will be empty so the container should be deleted. It looks like this already happens in the code, so this Jira is to add a unit test for this case as well.



--
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