hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6841) Meta prefetching is slower than doing multiple meta lookups
Date Thu, 20 Sep 2012 21:01:08 GMT

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

Lars Hofhansl commented on HBASE-6841:
--------------------------------------

Yeah the stuff we in HTable is a disaster (if you ask me... probably has to do with multiple
threads using HTables that share the same HConnection, not sure), but I think that's for another
patch.

The meaning of the flag is not changed, just the default (unless I made mistake in the patch).

                
> Meta prefetching is slower than doing multiple meta lookups
> -----------------------------------------------------------
>
>                 Key: HBASE-6841
>                 URL: https://issues.apache.org/jira/browse/HBASE-6841
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Jean-Daniel Cryans
>            Priority: Critical
>             Fix For: 0.94.2
>
>         Attachments: 6841-0.94.txt
>
>
> I got myself into a situation where I needed to truncate a massive table while it was
getting hits and surprisingly the clients were not recovering. What I see in the logs is that
every time we prefetch .META. we setup a new HConnection because we close it on the way out.
It's awfully slow.
> We should just turn it off or make it useful. jstacks coming up.

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