rjgoyln opened a new pull request, #11822: URL: https://github.com/apache/ozone/pull/11822
## What changes were proposed in this pull request? An FSO rename that touches the bucket root hands its response the same `OmBucketInfo` instance it just put into the bucket table cache, and the response serializes it later on the flush thread. Every other key request gives its response a copy; this makes the rename do the same. On master this is hardening rather than a live bug. Since HDDS-16161, requests that change bucket usage copy the cached bucket before changing it, so the double count and `QUOTA_EXCEEDED` on replay described in the JIRA no longer reproduce. ## What is the link to the Apache JIRA? https://issues.apache.org/jira/browse/HDDS-16770 ## How was this patch tested? - The new unit test fails on master (`expected: <0> but was: <1>`) and passes with the fix. - The JIRA's component-level reproduction (not included) is clean on master, triggers once key commit mutates the cached bucket in place again, and is clean with this fix. - Rename, key commit and double buffer unit tests (97), checkstyle and PMD pass. Generated-by: Claude Code (Opus 5.5) -- 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]
