[
https://issues.apache.org/jira/browse/HDFS-16737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600562#comment-17600562
]
ASF GitHub Bot commented on HDFS-16737:
---------------------------------------
ZanderXu commented on PR #4784:
URL: https://github.com/apache/hadoop/pull/4784#issuecomment-1237614839
@ayushtkn @jianghuazhu Sir, I added one UT to test the active count and
core pool size of the executer. Can you help me review it again.
I found this issue because we encountered many stacked pending deletion in
our prod environment and caused ReplicationNotFoundException. So this PR is
used to increase the active thread count of the executer. And we will raise
another PR to resolve ReplicationNotFoundException.
@ferhui @haiyang1987 Masters, can you help me review this PR?
> 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]
