hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-6471) Performance regression caused by HBASE-4054
Date Sun, 07 Apr 2013 04:41:20 GMT

     [ https://issues.apache.org/jira/browse/HBASE-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack updated HBASE-6471:
-------------------------

    Fix Version/s:     (was: 0.95.0)
                   0.94.2

Fix up after bulk move overwrote some 0.94.2 fix versions w/ 0.95.0 (Noticed by Lars Hofhansl)
                
> 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, trunk-6471_v2.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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message