NibiruXu

> a better approach might be to track deleted containers in RocksDB only. @errose28 My thought is also to do this. Some heavy load scenarios could be benefited from this....

> What is the expected behavior if there is only one replica left and it is unhealthy? By default, such containers will be left alone and ozone will do nothing...

> Hi @Xushaohong, I don't think we want to be deleting containers with all replicas unhealthy automatically, because this will cause divergence between the OM's metadata and the corresponding block...

> Adding to @kerneltime's response based on other discussions around this issue, it seems the desired solution would be to provide a path to remove containers from the system who...

We need a more complete patch, close it first

> Could you please describe how these blocks are being detected in the PR description - like a small design overview? Sure, will update later, I am working on fixing...

https://docs.google.com/document/d/1Oi1zPKdmvA7DFwIcUWz6zw_p-pY3D1L76gyV37jQT94/edit# The prototype of the design.

> Thx for the question~ @kaijchen The case for OpenKeyCleanupService is not related to the logic here. They should be two cases as I mentioned in the DOC.

Hi, all! I have done the refactor of this PR. Could you take a look ~

@kaijchen @errose28 Thx for the review! :)