You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/07/01 21:36:00 UTC
[jira] [Closed] (HBASE-14478) A ThreadPoolExecutor with a LinkedBlockingQueue cannot execute tasks concurrently
[ https://issues.apache.org/jira/browse/HBASE-14478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kyle Purtell closed HBASE-14478.
---------------------------------------
> A ThreadPoolExecutor with a LinkedBlockingQueue cannot execute tasks concurrently
> ---------------------------------------------------------------------------------
>
> Key: HBASE-14478
> URL: https://issues.apache.org/jira/browse/HBASE-14478
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Affects Versions: 2.0.0
> Reporter: Jingcheng Du
> Assignee: Jingcheng Du
> Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-14478.patch
>
>
> In FlushTableSubprocedurePool and SnapshotSubprocedurePool, the ThreadPoolExecutor with a LinkedBlockingQueue is used, and it's corePoolSize and maximumPoolSize are not the same, which can cause the if the number of tasks is larger than corePoolSize, those tasks cannot be executed until old tasks are finished and the number of running tasks is less than corePoolSize. We should use the same value for the corePoolSize and maximumPoolSize if the LinkedBlockingQueue is used.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)