[
https://issues.apache.org/jira/browse/HDDS-16699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-16699:
----------------------------------
Labels: pull-request-available (was: )
> S3G: Avoid calling getS3Volume in INIT_MULTIPART_UPLOAD
> -------------------------------------------------------
>
> Key: HDDS-16699
> URL: https://issues.apache.org/jira/browse/HDDS-16699
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Chung-En Lee
> Assignee: Huang Kuan Hao
> Priority: Major
> Labels: pull-request-available
>
> Background & Problem
> Initiating a multipart upload session (`POST /bucket/key?uploads`) in
> `ObjectEndpoint` currently requires calling `getS3VolumeContext` prior to
> issuing `initiateMultipartUpload` to OM.
> For big data workloads frequently opening concurrent multipart sessions, this
> extra lookup adds avoidable round-trip latency to each upload setup.
> Proposed Solution
> 1. Enable `assumeS3Context=true` in `OmKeyArgs` for the
> `InitiateMultipartUpload` RPC.
> 2. Refactor `ObjectEndpoint`'s MPU initiation codepath to bypass the
> standalone `getS3VolumeContext` lookup.
> Expected Impact
> Reduces initiation latency for multipart uploads by removing 1 RPC round trip.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
