Xushaohong commented on PR #3657: URL: https://github.com/apache/ozone/pull/3657#issuecomment-1231091793
> 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 have all replicas unhealthy or missing and **no keys mapped to them**, and that **the system should do this automatically without extra configuration**. My current understanding of this patch is that it is not doing the two parts in bold. Handling this is going to be a bit involved and may require a design document. I will try to write up some ideas to share out soon. Thx @errose28 for the reply, the auto-detection and cleanup is what we need. Currently, the single component either OM or SCM doesn't have the **map of keys to the container**. If the service is on SCM, it might need another query to OM to check if the container remains some keys. One concern is that such a map is only available in the recon API, which is not clear enough and not commonly used. -- 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]
