hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-14478) A ThreadPoolExecutor with a LinkedBlockingQueue cannot execute tasks concurrently
Date Fri, 25 Sep 2015 17:47:04 GMT

     [ https://issues.apache.org/jira/browse/HBASE-14478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

ramkrishna.s.vasudevan updated HBASE-14478:
-------------------------------------------
      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

Pushed to master. Thanks for the patch [~jingcheng.du@intel.com] and others for the reviews.


> 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
>             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
(v6.3.4#6332)

Mime
View raw message