[
https://issues.apache.org/jira/browse/HDDS-16701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dino2895 reassigned HDDS-16701:
-------------------------------
Assignee: dino2895
> S3G: Avoid calling getS3Volume in DELETE_KEY
> --------------------------------------------
>
> Key: HDDS-16701
> URL: https://issues.apache.org/jira/browse/HDDS-16701
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Chung-En Lee
> Assignee: dino2895
> Priority: Major
>
> Background & Problem
> In `ObjectEndpoint#delete`, deleting a single object triggers a
> `getS3VolumeContext` RPC before invoking `deleteKey` on OM. For workloads
> that execute high volumes of individual S3 deletes, doubling the RPC count
> severely degrades throughput and adds queue pressure to OM.
> Proposed Solution
> 1. Propagate `assumeS3Context=true` into `OmKeyArgs` used by `deleteKey`.
> 2. Allow OM to resolve the S3 volume context directly during single key
> deletion.
> 3. Remove the explicit `getS3VolumeContext` call in S3G's delete handler.
> Expected Impact
> Cuts single-object deletion RPC overhead by 50% (from 2 RPCs down to 1).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
