[
https://issues.apache.org/jira/browse/HDFS-14367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105422#comment-17105422
]
Ayush Saxena commented on HDFS-14367:
-------------------------------------
Committed to trunk, branch-3.3, 3.2 and 3.1
Thanx [~glove747] for the contribution!!!
> EC: Parameter maxPoolSize in striped reconstruct thread pool isn't affecting
> number of threads
> ----------------------------------------------------------------------------------------------
>
> 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
> Assignee: 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
