You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/10/20 20:39:12 UTC
[jira] [Updated] (HDDS-4371) Datanode should have deletion service
thread per volume
[ https://issues.apache.org/jira/browse/HDDS-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ethan Rose updated HDDS-4371:
-----------------------------
Target Version/s: 1.3.0 (was: 1.2.0)
I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.
If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.
> Datanode should have deletion service thread per volume
> -------------------------------------------------------
>
> Key: HDDS-4371
> URL: https://issues.apache.org/jira/browse/HDDS-4371
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: Ozone Datanode
> Reporter: Lokesh Jain
> Assignee: YI-CHEN WANG
> Priority: Major
>
> Datanode currently maintains a thread pool of configured number of threads in BlockDeletingService. For better parallelism it is better to have a deletion thread or service per volume.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org