sodonnel opened a new pull request, #5523: URL: https://github.com/apache/ozone/pull/5523
## What changes were proposed in this pull request? If a container appears empty to SCM (ie key count is zero in the containerInfo) and there are no replicas, it could be a container which failed to be created on the datanodes, and no replicas will ever be reported. However there isn't enough information to know if the container can be safely deleted or not, as the DN could have gone offline or missed some heartbeats etc. As things stand, such as container will appear as missing in the container report. In this PR, we change that to leave the container as CLOSED but count it as EMPTY without triggering the delete process. That means if replicas later appear, it will be OK. However if the replicas never appear, the container will be stuck in this state forever. Additionally, if there **should** be replicas, as the client successfully wrote to the DNs and updated OM, there is no way to know this on SCM and the container should really be missing despite it being logged as empty, hiding the problem. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-9550 ## How was this patch tested? New unit test added -- 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]
