You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2015/09/14 22:25:46 UTC

[jira] [Commented] (HBASE-10449) Wrong execution pool configuration in HConnectionManager

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

stack commented on HBASE-10449:
-------------------------------

Back again [~nkeywal]

I'm looking at failing tests and see thread dumps with pools of 256 threads per client instance.

Where does 'Create a single thread, queue all the tasks for this thread.' come from?

Our 'core' setting is same as our 'max' so we will keep spinning new threads until we hit max whether all of the other 255 are idle or not. That seems wrong (it is for sure a PITA looking at thread dumps of 256 threads doing nought.

I opened new issue HBASE-14433 for discussion.

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