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

Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2015/04/11 02:31:13 UTC

[jira] [Updated] (HBASE-6841) Meta prefetching is slower than doing multiple meta lookups

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

Andrew Purtell updated HBASE-6841:
----------------------------------
    Resolution: Cannot Reproduce
        Status: Resolved  (was: Patch Available)

Reopen if still an issue with current code

> 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
>         Attachments: 6841-0.94.txt, 6841-0.96.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 was sent by Atlassian JIRA
(v6.3.4#6332)