[
https://issues.apache.org/jira/browse/HBASE-10449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14768844#comment-14768844
]
Nicolas Liochon commented on HBASE-10449:
-----------------------------------------
What's happening for the expire is:
- we have a 60s timeout with 256 seconds.
- let's imagine we have 1 query per second. We will still have 60 threads,
because each new request will create a new thread until we reach coreSize. As
the timeout is 60s, the oldest threads will expire after 60s.
I haven't double-checked, but I believe that the threads are needed because of
the old i/o pattern. So we do need a max in the x00 range (it's like this since
0.90 at least. In theory, it's good for small cluster (100 nodes), but not as
good if the cluster is composed of thousands of nodes)
I did actually spent some time on this a year ago, in HBASE-11590. @stack, what
do you think of the approach? I can finish the work I started there. But I will
need a review. There are also some ideas/hacks in
http://stackoverflow.com/questions/19528304/how-to-get-the-threadpoolexecutor-to-increase-threads-to-max-before-queueing/19528305#19528305
I haven't reviewed them yet.
> 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)
