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

Sammi Chen commented on HDDS-7728:
----------------------------------

Hi [~sodonnell], [~erose],  I'm not sure if we are thinking the same case, 
could you explain a little bit more about what the orphan block and orphan 
container situations mentioned, and how is it related with the current proposal 
that if there are 4 replicas of a over replicated container, which one is a 
better candidate to delete? So that we can on the same page and continue the 
discussion. 

I understand that RM is a module with a lot of complexity.  But Recon also 
become more and more complex now. Is it possible for Recon to make a better 
decision than RM without knowing all the information which are easy to get by 
RM?  I'm kind of doubt that. 

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

Reply via email to