[
https://issues.apache.org/jira/browse/HDDS-9095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-9095:
------------------------------
Description:
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 expired
threshold).
was:
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.
> Implement cleanup service for MultipartInfoTable
> ------------------------------------------------
>
> 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 expired threshold).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
