[
https://issues.apache.org/jira/browse/HDDS-15079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai resolved HDDS-15079.
-------------------------------------
Resolution: Duplicate
> Make DirectoryDeletingService multi-threaded
> --------------------------------------------
>
> Key: HDDS-15079
> URL: https://issues.apache.org/jira/browse/HDDS-15079
> Project: Apache Ozone
> Issue Type: Bug
> Components: OM
> Reporter: Saketa Chalamchala
> Assignee: Saketa Chalamchala
> Priority: Major
>
> After HDDS-13034 there was a the deletion thread pool executor that was meant
> to parallelize deletes per store ends up spawning only one thread and
> scheduling all delete tasks on that single thread regardless of what
> `numberOfParallelThreadsPerStore` is configured to.
> This is because the workerQueue is unbounded and it only spawns a new thread
> beyond the core pool size, 0 if the queue rejects the task (which is never
> because it is unbounded).
> {code:java}
> this.deletionThreadPool = new ThreadPoolExecutor(0,
> numberOfParallelThreadsPerStore,
> interval, unit, new LinkedBlockingDeque<>(Integer.MAX_VALUE));
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]