You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2012/08/14 06:57:38 UTC
[jira] [Commented] (HBASE-6471) Performance regression caused by
HBASE-4054
[ https://issues.apache.org/jira/browse/HBASE-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433888#comment-13433888 ]
Lars Hofhansl commented on HBASE-6471:
--------------------------------------
Looks good to me.
> Performance regression caused by HBASE-4054
> -------------------------------------------
>
> Key: HBASE-6471
> URL: https://issues.apache.org/jira/browse/HBASE-6471
> Project: HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.92.0
> Reporter: Lars George
> Assignee: Jimmy Xiang
> Priority: Critical
> Fix For: 0.94.2
>
> Attachments: trunk-6471.patch, trunk-6471.patch
>
>
> The patch in HBASE-4054 switches the PooledHTable to extend HTable as opposed to implement HTableInterface.
> Since HTable does not have an empty constructor, the patch added a call to the super() constructor, which though does trigger the ZooKeeper and META scan, causing a considerable delay.
> With multiple threads using the pool in parallel, the first thread is holding up all the subsequent ones, in effect it negates the whole reason we have a HTable pool.
> We should complete HBASE-5728, or alternatively add a protected, empty constructor the HTable. I am +1 for the former.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira