[
https://issues.apache.org/jira/browse/HDDS-11699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-11699:
-------------------------------
Description:
HDDS-9654 added support for ranged GET request for specified part. However,
currently it's implemented by filtering the OmKeyInfoLocation based on the
partNumber in client side (RpcClient). Therefore, for a large MPU key (few
hundred GBs with many parts), it still requires OM to send the whole
List<OmKeyLocationInfo> for every S3 part GET request.
We can implement the filter from the OM side (server side) to reduce the
network overhead. See
https://github.com/apache/ozone/pull/7419#issuecomment-2467650696
Note: This change will require some additional communication protocol between
S3G and OM. Therefore, it's most likely that we need to add a new
OzoneManagerVersion to preserve compatibility.
was:
HDDS-9654 added support for ranged GET request for specified part. However,
currently it's implemented by filtering the OmKeyInfoLocation based on the
partNumber in client side (RpcClient). Therefore, for a large MPU key (few
hundred GBs with many parts), it still requires OM to send the whole
List<OmKeyLocationInfo> for every S3 part GET request.
We can implement the filter from the OM side (server side) to reduce the
network overhead.
Note: This change will require some additional communication protocol between
S3G and OM. Therefore, it's most likely that we need to add a new
OzoneManagerVersion to preserve compatibility.
> OM support for ranged GET request for a specified part
> ------------------------------------------------------
>
> Key: HDDS-11699
> URL: https://issues.apache.org/jira/browse/HDDS-11699
> Project: Apache Ozone
> Issue Type: Improvement
> Components: OM, s3gateway
> Reporter: Ivan Andika
> Priority: Major
>
> HDDS-9654 added support for ranged GET request for specified part. However,
> currently it's implemented by filtering the OmKeyInfoLocation based on the
> partNumber in client side (RpcClient). Therefore, for a large MPU key (few
> hundred GBs with many parts), it still requires OM to send the whole
> List<OmKeyLocationInfo> for every S3 part GET request.
> We can implement the filter from the OM side (server side) to reduce the
> network overhead. See
> https://github.com/apache/ozone/pull/7419#issuecomment-2467650696
> Note: This change will require some additional communication protocol between
> S3G and OM. Therefore, it's most likely that we need to add a new
> OzoneManagerVersion to preserve compatibility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
