Chung-En Lee created HDDS-16702:
-----------------------------------

             Summary: S3G: Avoid calling getS3Volume in MULTI_DELETE
                 Key: HDDS-16702
                 URL: https://issues.apache.org/jira/browse/HDDS-16702
             Project: Apache Ozone
          Issue Type: Sub-task
            Reporter: Chung-En Lee


Background & Problem
In `MultiDeleteEndpoint`, S3G receives a batch delete request and invokes 
`getS3VolumeContext` before executing deletions. While batch delete handles 
multiple keys at once, the initial volume resolution step is still redundant 
and can be handled directly by OM.

Proposed Solution
1. Allow OM's batch deletion handler (`deleteKeys` / `OmDeleteKeysRequest`) to 
accept S3 bucket context natively via `assumeS3Context=true`.
2. Refactor `MultiDeleteEndpoint` to eliminate the preliminary 
`getS3VolumeContext` call.

Expected Impact
Eliminates the initial lookup RTT before batch delete processing starts.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to