[
https://issues.apache.org/jira/browse/HDDS-11510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Kumar updated HDDS-11510:
--------------------------------
Parent: (was: HDDS-11506)
Issue Type: Bug (was: Sub-task)
> All deletion services should support multiple threads
> -----------------------------------------------------
>
> Key: HDDS-11510
> URL: https://issues.apache.org/jira/browse/HDDS-11510
> Project: Apache Ozone
> Issue Type: Bug
> Components: OM, SCM
> Reporter: Ethan Rose
> Assignee: Aryan Gupta
> Priority: Major
>
> When a large amount of data is deleted, we may see slow progress to clear it
> out due to the large backlog of pending deletes, even if all deletion
> services are running for their full intervals and collecting their maximum
> number of entries. In order to speed up deletion further, more threads will
> need to be configured. However, the deletion algorithms in OM and SCM
> currently only support single threaded implementations. The algorithms for
> these jobs need to be updates to partition the pending delete key space to
> support any number of deletion threads working over it.
> This Jira is relevant for the following components and these may be done in
> separate subtasks:
> * OM open key cleanup
> * OM key delete
> * OM directory delete
> * SCM block delete
> Datanode block deletion already supports a configurable thread pool that
> divides work by container.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
