[
https://issues.apache.org/jira/browse/HDDS-9095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18057301#comment-18057301
]
Ivan Andika edited comment on HDDS-9095 at 2/9/26 8:39 AM:
-----------------------------------------------------------
> Agree we should not throw exception instead continue and remove entry from
> multipartInfoTable
Would you like to work on it? If not, you can raise a ticket and assign it to
me. Else, I can hep to review.
> We can have tool as well to clear these entries manually if someone is not
> using the latest version
I don't think it's necessary. This issue only happens for very old keys and
should not happen since 1.4.0 (when this feature is deployed). I'd prefer to
simply remove the check.
was (Author: JIRAUSER298977):
> Agree we should not throw exception instead continue and remove entry from
> multipartInfoTable
Would you like to work on it? If not, you can raise a ticket and assign it to
me.
> We can have tool as well to clear these entries manually if someone is not
> using the latest version
I don't think it's necessary. This issue only happens for very old keys and
should not happen since 1.4.0 (when this feature is deployed). I'd prefer to
simply remove the check.
> Cleanup expired incomplete MPUs
> -------------------------------
>
> Key: HDDS-9095
> URL: https://issues.apache.org/jira/browse/HDDS-9095
> Project: Apache Ozone
> Issue Type: Improvement
> Components: OM
> Reporter: Ivan Andika
> Assignee: Ivan Andika
> Priority: Major
> Fix For: 1.4.0
>
>
> In our cluster, there are around few thousands MPU keys in
> multipartInfoTable, with some of them being few months old.
> The reason is that these MPU keys are already initiated, and possibly
> committed few parts, but was not completed / aborted by the user. These
> spaces can be freed.
> Similar to the cleanup service OM open key table (HDDS-4120), we can
> implement clean up on MultipartInfoTable (and related open keys in
> OpenKeyTable) using a background job. -However, instead of using a new OM
> request / response, we can reuse the OM MPU abort request / response instead,
> which already handles the cleanup (i.e. expired inflight MPU can be aborted
> after a defined expiry threshold).-
>
> This is similar to {{AbortIncompleteMultipartUpload}} lifecycle
> configurations in AWS S3
> ([https://aws.amazon.com/blogs/aws-cloud-financial-management/discovering-and-deleting-incomplete-multipart-uploads-to-lower-amazon-s3-costs/]).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
