[
https://issues.apache.org/jira/browse/HDDS-7732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17722097#comment-17722097
]
Stephen O'Donnell commented on HDDS-7732:
-----------------------------------------
Looking at HDDS-7126 the changes there will handled "deleted" EC containers
too, as it just check the start of the container is DELETED, so there is
nothing to do there.
An EC container which is "MISSING" will still get marked DELETING provided all
the remaining "key replicas" report as empty. A key replica is replicaIndex=1
or any parityIndex. We cannot trigger deleting on a non key replica, as they
may have less blocks than the key replicas due to partial stripes in the EC
files.
This means we could still get a case where all the blocks are technically
deleted, but we don't know that as all the key replicas are missing, but then
the container will be reported as MISSING by RM, and someone will need to take
some action to fix that, or we need to add support for dealing with MISSING
containers into the system - ie a way to remove them.
I don't think there is any code we can add to deal with unrecoverable EC
containers which also should get marked as deleting, but cannot due to the all
"key replicas" being lost.
I have added a simple unit test that proves an unrecoverable EC container which
is also empty is transitioned to DELETING in the PR. Aside from that, I don't
think there is anything else to do here.
> 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: [email protected]
For additional commands, e-mail: [email protected]
