hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-9917) Fix it so Default Connection Pool does not spin up max threads even when not needed
Date Fri, 08 Nov 2013 00:13:17 GMT

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

stack updated HBASE-9917:
-------------------------

    Attachment: pool.txt

Small patch.  Adds a core thread count and smaller keep alive.  Also gives the pool threads
a (shorter) name tied to the HConnection instance.  Finally, queue size is tied to max thread
size.

> 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: 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)

Mime
View raw message