[jira] [Commented] (HDFS-16737) Fix number of threads in FsDatasetAsyncDiskService#addExecutorForVolume

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HDFS-16737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582999#comment-17582999 ] 

ASF GitHub Bot commented on HDFS-16737:
---------------------------------------

ZanderXu opened a new pull request, #4784:
URL: https://github.com/apache/hadoop/pull/4784

   ### Description of PR
   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.
   
   




> 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
>
> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org