[
https://issues.apache.org/jira/browse/HDFS-16737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17597223#comment-17597223
]
ASF GitHub Bot commented on HDFS-16737:
---------------------------------------
ZanderXu commented on PR #4784:
URL: https://github.com/apache/hadoop/pull/4784#issuecomment-1230394854
@ayushtkn Thanks for your review. About
[HDFS-16386](https://issues.apache.org/jira/browse/HDFS-16386), the increased
memory maybe caused by the stacked async deletion takes, increasing or
decreasing the maximum number of threads may cannot fix it. Can increase the
corePoolSize of the threadPoolExecutor maybe can reduce the memory.
cc @jianghuazhu
I have updated the patch, please help me review it again. Thanks
> Fix number of threads in FsDatasetAsyncDiskService#addExecutorForVolume
> -----------------------------------------------------------------------
>
> Key: HDFS-16737
> URL: https://issues.apache.org/jira/browse/HDFS-16737
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: ZanderXu
> Assignee: ZanderXu
> Priority: Major
> Labels: pull-request-available
>
> The number of threads in FsDatasetAsyncDiskService#addExecutorForVolume is
> elastic right now, make it fixed.
> Presently the corePoolSize is set to 1 and maximumPoolSize is set to
> maxNumThreadsPerVolume, but since the size of Queue is Integer.MAX, the queue
> doesn't tend to get full and threads are always confined to 1 irrespective of
> maxNumThreadsPerVolume.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
