[ https://issues.apache.org/jira/browse/HDFS-14367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guo Lei updated HDFS-14367: --------------------------- Description: The thread number increase to maximumPoolSize only when the workQueue is full. 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,       numThreads, 60, new LinkedBlockingQueue<>(),       "StripedBlockReconstruction-", false);   stripedReconstructionPool.allowCoreThreadTimeOut(true); } was:The thread number increase to maximumPoolSize only when the workQueue is full. > 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 > > The thread number increase to maximumPoolSize only when the workQueue is full. > 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, >       numThreads, 60, new LinkedBlockingQueue<>(), >       "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