hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Liochon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10449) Wrong execution pool configuration in HConnectionManager
Date Wed, 16 Sep 2015 21:28:46 GMT

    [ https://issues.apache.org/jira/browse/HBASE-10449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791145#comment-14791145
] 

Nicolas Liochon commented on HBASE-10449:
-----------------------------------------

It's the former: in this case, the queries are queued. A new thread will be created only when
the queue is full. Then, if we reach maxThreads and the queue is full the new tasks are rejected.
In our case the queue is nearly unbounded, so we stay with corePoolSize.

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

Mime
View raw message