[
https://issues.apache.org/jira/browse/HDFS-16737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18035476#comment-18035476
]
ASF GitHub Bot commented on HDFS-16737:
---------------------------------------
github-actions[bot] commented on PR #4784:
URL: https://github.com/apache/hadoop/pull/4784#issuecomment-3488542844
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> 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]
