[
https://issues.apache.org/jira/browse/HDDS-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17766689#comment-17766689
]
Ashish Kumar commented on HDDS-7728:
------------------------------------
There are two different cases:
*Missing/Orphan Containers*
In case of missing/orphan containers I agree with Ethan's proposal that Recon
should identify and instruct SCM/DN to remove those containers. As recon
already have information from OM/DN, and in future recon can take decision to
do this orphan container cleanup.
*Orphan Blocks inside Container*
When there are 4 replica, and 1 replica has orphan blocks. And assuming SCM
deletes one replica which has orphan blocks.If we want to cleanup orphan blocks
from closed containers using recon. In this case closed container
responsibility is distributed across two service. Some delete can come from
recon and some from SCM for the same container.
But the other way SCM can keep track of block delete transaction ID at replica
level, and then delete replica based on this. It can keep responsibility with
SCM for closed containers.
> Block should be safely deleted from the containers if they are instructed
> from OM and containers are in missing state.
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: HDDS-7728
> URL: https://issues.apache.org/jira/browse/HDDS-7728
> Project: Apache Ozone
> Issue Type: Improvement
> Components: SCM
> Affects Versions: 1.3.0
> Reporter: Uma Maheswara Rao G
> Assignee: Ashish Kumar
> Priority: Major
>
> Currently when OM instructs to delete the blocks and if containers are in
> missing state, deletion may not be processed properly. This Jira to track
> this requirement and implement to safe deletion os blocks what ever state
> they are on. Otherwise containers would never get cleaned up even though all
> blocks in that files deleted.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
