hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Liochon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10018) Change the location prefetch
Date Mon, 03 Mar 2014 17:19:22 GMT

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

Nicolas Liochon commented on HBASE-10018:
-----------------------------------------

I reproduce the issue, it's a table not found on hbase:namespace when there is a master copro.
Looking.

> Change the location prefetch
> ----------------------------
>
>                 Key: HBASE-10018
>                 URL: https://issues.apache.org/jira/browse/HBASE-10018
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.98.0, 0.96.0
>            Reporter: Nicolas Liochon
>            Assignee: Nicolas Liochon
>             Fix For: 0.99.0
>
>         Attachments: 10018.v1.patch, 10018.v2.patch, 10018v3.patch
>
>
> Issues with prefetching are:
> - we do two calls to meta: one for the exact row, one for the prefetch 
> - it's done in a lock
> - we take the next 10 regions. Why 10, why the 10 next?
> - is it useful if the table has 100K regions?
> Options are:
> - just remove it
> - replace it with a reverse scan: this would save a call
>  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message