[
https://issues.apache.org/jira/browse/HDDS-16700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18125941#comment-18125941
]
Chi-Hsuan Huang commented on HDDS-16700:
----------------------------------------
Just a thought for this and HDDS\-16701 to HDDS\-16703:
[https://github.com/apache/ozone/pull/11449|https://github.com/apache/ozone/pull/11449]
resolves the S3 volume in {{OzoneManagerRatisUtils#createClientRequest}} for
abort MPU. These ops may need the same rewrite, so it could be a good time to
extract a shared helper here. Just sharing in case it helps.
> S3G: Avoid calling getS3Volume in PUT_OBJECT_TAGGING
> ----------------------------------------------------
>
> Key: HDDS-16700
> URL: https://issues.apache.org/jira/browse/HDDS-16700
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Chung-En Lee
> Assignee: dino2895
> Priority: Major
>
> Background & Problem
> When applying tags via `PUT /bucket/key?tagging`, S3G queries
> `getS3VolumeContext` before invoking `putObjectTagging` on OM. Setting tags
> is a standalone metadata mutation, making the preparatory volume lookup RPC
> redundant.
> Proposed Solution
> 1. Extend `assumeS3Context=true` to `OmKeyArgs` for object tagging mutations
> on OM.
> 2. Remove the preliminary `getS3VolumeContext` RPC in `ObjectEndpoint#put`
> (tagging path).
> Expected Impact
> Reduces RPC round trips from 2 to 1 for `PutObjectTagging` calls.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
