andyhuangdev opened a new pull request, #11901: URL: https://github.com/apache/ozone/pull/11901
## What changes were proposed in this pull request? SCM can delete a QUASI_CLOSED container when all known replicas are empty, even if their sequence IDs are below the container’s sequence ID. A replica containing committed data may be offline and later be force deleted when it returns. This patch preserves the container and its replicas when the highest known replica sequence ID is below the container’s sequence ID. Deletion remains allowed once an empty replica reaches that sequence ID. Containers that never received writes remain eligible for deletion. This guard relies on the sequence ID currently held by SCM; it does not address sequence ID persistence across SCM restarts or the report-processing order during resurrection. ## What is the link to the Apache JIRA [HDDS-16809](https://issues.apache.org/jira/browse/HDDS-16809) ## How was this patch tested? - Added a regression test and confirmed it failed before the fix. - Verified that lagging empty replicas are preserved and deletion proceeds once an empty replica reaches the container’s sequence ID. - Passed 182 tests covering empty, deleting, and quasi-closed container handlers, replication manager, and full and incremental container reports. - Passed repository checkstyle. -- 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]
