hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15784) Misuse core/maxPoolSize of LinkedBlockingQueue in ThreadPoolExecutor
Date Wed, 18 May 2016 12:43:12 GMT

    [ https://issues.apache.org/jira/browse/HBASE-15784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288893#comment-15288893
] 

Hudson commented on HBASE-15784:
--------------------------------

FAILURE: Integrated in HBase-Trunk_matrix #928 (See [https://builds.apache.org/job/HBase-Trunk_matrix/928/])
HBASE-15784 Misuse core/maxPoolSize of LinkedBlockingQueue in (ramkrishna: rev 7b5d5394c08e4d5a18c8f9fc62b45930bf892f41)
* hbase-server/src/test/resources/hbase-site.xml
* hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsckReplicas.java
* hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift/TBoundedThreadPoolServer.java
* hbase-client/src/test/resources/hbase-site.xml
* hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionImplementation.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/HFileReplicator.java
* hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift/ThriftServerRunner.java
* hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsckTwoRS.java
* hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsckMOB.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/RegionReplicaReplicationEndpoint.java
* hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsckOneRS.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/util/MultiHConnection.java


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

Mime
View raw message