You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Guo Lei (JIRA)" <ji...@apache.org> on 2019/03/15 06:47:00 UTC
[jira] [Commented] (HDFS-14367) Useless parameter maxPoolSize in
striped reconstruct thread pool
[ https://issues.apache.org/jira/browse/HDFS-14367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793369#comment-16793369 ]
Guo Lei commented on HDFS-14367:
--------------------------------
[~2012ecs41@smvdu.ac.in] PTAL
> Useless parameter maxPoolSize in striped reconstruct thread pool
> ----------------------------------------------------------------
>
> Key: HDFS-14367
> URL: https://issues.apache.org/jira/browse/HDFS-14367
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ec
> Affects Versions: 3.3.0
> Reporter: Guo Lei
> Priority: Major
> Attachments: HDFS-14367.001.patch
>
>
> The workQueue length wasn't specified, so the thread number never be increase.
> The thread number increase to maximumPoolSize only when the workQueue is full.
> file location: org/apache/hadoop/hdfs/server/datanode/erasurecode/ErasureCodingWorker.java
> private void initializeStripedBlkReconstructionThreadPool(int numThreads) {
> LOG.debug("Using striped block reconstruction; pool threads={}",
> numThreads);
> stripedReconstructionPool = DFSUtilClient.getThreadPoolExecutor(2,
> {color:#ff0000}numThreads{color}, 60, {color:#ff0000}new LinkedBlockingQueue<>(){color},
> "StripedBlockReconstruction-", false);
> stripedReconstructionPool.allowCoreThreadTimeOut(true);
> }
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org