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-15784) Misuse core/maxPoolSize of LinkedBlockingQueue in ThreadPoolExecutor
Date Wed, 18 May 2016 07:12:13 GMT

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

ramkrishna.s.vasudevan updated HBASE-15784:
    Fix Version/s: 2.0.0

Thanks for the patch [~jingcheng.du@intel.com]. Thanks all for the reviews.

> Misuse core/maxPoolSize of LinkedBlockingQueue in ThreadPoolExecutor
> --------------------------------------------------------------------
>                 Key: HBASE-15784
>                 URL: https://issues.apache.org/jira/browse/HBASE-15784
>             Project: HBase
>          Issue Type: Bug
>          Components: Client, Replication, Thrift
>            Reporter: Jingcheng Du
>            Assignee: Jingcheng Du
>             Fix For: 2.0.0
>         Attachments: HBASE-15784-v2.patch, HBASE-15784.patch
> LinkedBlockingQueue is usually used in ThreadPoolExecutor. It allows the thread pool
not to be blocked if the number of running threads in the pool is less than the max pool size
and the queue is not full.
> But when the core pool size of ThreadPoolExecutor is different from the max pool size,
the things don't go as expected. When the number of running threads is the same with the core
size, more requests of executions are added into the LinkedBlockingQueue. And the requests
can be executed again only when LinkedBlockingQueue is full or some of running threads are
> Thus it is better to use the same value for the core and max pool size when the LinkedBlockingQueue
is used.

This message was sent by Atlassian JIRA

View raw message