[
https://issues.apache.org/jira/browse/HBASE-10449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746919#comment-14746919
]
Nicolas Liochon commented on HBASE-10449:
-----------------------------------------
Actually I'm having two doubts:
- the core threads should already have this timeout, no. We should not see 256
threads, because they should expire already
- IIRC, this thread pool is used when connecting to the various regionserver,
and they block until they have an answer. So with 4 core threads (for example),
it means that if we do a multi we contact 4 servers simultaneously at most. The
threads are not really using CPUs, they're waiting (old i/o style). BUt may be
it has changed?
> Wrong execution pool configuration in HConnectionManager
> --------------------------------------------------------
>
> Key: HBASE-10449
> URL: https://issues.apache.org/jira/browse/HBASE-10449
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.98.0, 0.99.0, 0.96.1.1
> Reporter: Nicolas Liochon
> Assignee: Nicolas Liochon
> Priority: Critical
> Fix For: 0.98.0, 0.96.2, 0.99.0
>
> Attachments: HBASE-10449.v1.patch
>
>
> There is a confusion in the configuration of the pool. The attached patch
> fixes this. This may change the client performances, as we were using a
> single thread.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
