hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10449) Wrong execution pool configuration in HConnectionManager
Date Mon, 03 Feb 2014 18:14:10 GMT

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

Nick Dimiduk commented on HBASE-10449:
--------------------------------------

[~nkeywal] I have no objection to the change in default as I have no evidence to argue for
one value or another. I do find it strange that this default changes as part of a point release
on 0.96. [~stack]: it appears the default for hbase.hconnection.threads.core on 0.96, 0.98,
and trunk is now 256. An administrator can attain the 8 * cores behavior by setting this configuration
value to 0.

> 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.1.5#6160)

Mime
View raw message