[
https://issues.apache.org/jira/browse/HDDS-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17764483#comment-17764483
]
Ashish Kumar commented on HDDS-7728:
------------------------------------
Yes there are three cases we were thinking:
1) Missing state container: Which this Jira talks about, but according to
current code it will delete blocks whenever container comes back.
2) Under replicated: Already [~aryangupta1998] is fixing in
[HDDS-4368|https://issues.apache.org/jira/browse/HDDS-4368] . By this week he
will have the PR out.
3) Over replicated: This we thought of using deleteTransactionID and RM can
delete replica based on lowest blockDeleteTransactionID instead of deleting any
random replica. But currently we don't have blockDeleteTransactionID in replica
which RM can make use of for deciding which replica to delete?
In missing state container, container info as well as delete block transaction
will stuck forever if container never comes back. Yes there should be some
system which handles all these cases for cleaning up orphan blocks, missing
container etc.
> 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]
