[
https://issues.apache.org/jira/browse/HBASE-9917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820444#comment-13820444
]
Hudson commented on HBASE-9917:
-------------------------------
SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #835 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/835/])
HBASE-9917 Fix it so Default Connection Pool does not spin up max threads even
when not needed (stack: rev 1540945)
*
/hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java
> Fix it so Default Connection Pool does not spin up max threads even when not
> needed
> -----------------------------------------------------------------------------------
>
> Key: HBASE-9917
> URL: https://issues.apache.org/jira/browse/HBASE-9917
> Project: HBase
> Issue Type: Sub-task
> Components: Client
> Reporter: stack
> Assignee: stack
> Fix For: 0.98.0, 0.96.1
>
> Attachments: 9917.txt, pool.txt
>
>
> Testing, I noticed that if we use the HConnection executor service as opposed
> to the executor service that is created when you create an HTable without
> passing in a connection: i.e
> HConnectionManager.createConnection(config).getTable(tableName)
> vs
> HTable(config, tableName)
> ... then we will spin up the max 256 threads and they will just hang out
> though not being used.
> We are encouraging HConnection#getTable over new HTable so worth fixing.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
