rich7420 opened a new pull request, #11395:
URL: https://github.com/apache/ozone/pull/11395

   ## What changes were proposed in this pull request?
   
   Deleting a RECOVERING container removes it from the container set but leaves 
its recovery deadline in `recoveringContainerMap` until the background scrub 
removes it.
   
   Remove the recovering entry during deletion under the existing container 
write lock, matching the cleanup performed when closing a container. Add a test 
that force-deletes a RECOVERING container and checks both maps.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-16460
   
   ## How was this patch tested?
   
   - [Full fork CI](https://github.com/rich7420/ozone/actions/runs/35581757299) 
passed on `3ccd783c`.
   - Applied the patch to current master (`ae281be314`): `TestKeyValueHandler` 
and `TestContainerSet` passed, 57 tests total. Without the production fix, 
`testDeleteRecoveringContainer` fails because the recovery entry remains.
   - [TestKeyValueHandler 
10×10](https://github.com/rich7420/ozone/actions/runs/37107632729) is running.
   
   Generated-by: Codex (GPT-6)
   


-- 
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]

Reply via email to