slfan1989 commented on PR #7249: URL: https://github.com/apache/ozone/pull/7249#issuecomment-2413164585
> > The actual purpose of this PR is to make deletions orderly. If a certain container does not meet the conditions for deletion, we will ignore it until it satisfies the deletion conditions (i.e., when all DNs are healthy). > > This makes sense when we have enough containers to delete(during SCM delete iteration) for which all DNs are healthy, my only point is at some point when when there are only containers left which doesn't satisfy this condition, whether we should wait for all DNs to become healthy or just proceed with the deletion for the available healthy DNs at that point? @ashishkumar50 I believe waiting for all data nodes (DNs) to be ready before proceeding with deletion is a better choice. In the case of 3 replicas, it's acceptable for SCM to wait, but for EC-6-3, it’s less friendly. If one DN has an issue, the deletion of containers on the other 8 DNs will be affected. Issuing delete commands to these 8 DNs will occupy their deletion queues, leading to slower deletion of other containers. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
