[
https://issues.apache.org/jira/browse/HBASE-10449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746875#comment-14746875
]
Nicolas Liochon commented on HBASE-10449:
-----------------------------------------
> Where does 'Create a single thread, queue all the tasks for this thread.'
> come from?
This is what HBASE-9917 actually implemented: with the ThreadPoolExecutor if
the task queue is unbounded, it does not create new threads:
From:
http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ThreadPoolExecutor.html
If fewer than corePoolSize threads are running, the Executor always prefers
adding a new thread rather than queuing.
If corePoolSize or more threads are running, the Executor always prefers
queuing a request rather than adding a new thread.
If a request cannot be queued, a new thread is created unless this would exceed
maximumPoolSize, in which case, the task will be rejected.
But having less than 256 threads is fine. This was just restoring the previous
value.
> 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)
