rich7420 opened a new pull request, #11740: URL: https://github.com/apache/ozone/pull/11740
## What changes were proposed in this pull request? Single-object S3 DELETE resolves the S3 volume with a separate `GetS3VolumeContext` RPC before `DeleteKey`. This change sends `DeleteKey` with the existing `assumeS3Context` flag and lets OM resolve the volume before selecting the bucket layout. Conditional deletes and expected bucket owner checks are preserved. Requests with an expected owner reuse the volume resolved for the owner check; clients connected to older OMs retain the volume lookup fallback. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-16701 ## How was this patch tested? - [Fork CI](https://github.com/rich7420/ozone/actions/runs/40089120475) passed. - [10×10 flaky-test-check](https://github.com/rich7420/ozone/actions/runs/40089207844) for `TestMultiTenantVolume#testS3TenantVolume`: 100 runs, no failures or skips. - `TestOMKeyDeleteRequest#testS3VolumeContextBeforeLayoutSelection` and its inherited FSO variant: all 4 cases pass; reverting OM volume resolution makes the 2 S3-context cases fail. - Local S3 HTTP traces over Hadoop RPC, with security disabled and empty objects: DELETE without conditional or expected-owner headers goes from `GetS3VolumeContext` + `DeleteKey` to `DeleteKey` (2 → 1 OM RPC). -- 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]
