[
https://issues.apache.org/jira/browse/HBASE-10018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13831607#comment-13831607
]
stack commented on HBASE-10018:
-------------------------------
bq. . If nobody disagrees, I will do that: "make it optional, deactivated by
default, on .96 and .98."
Fine by me. Since you are of a jacobin bent, you could remove in 0.98 and just
configure it off in 0.96?
> 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
> Priority: Minor
> Fix For: 0.98.0, 0.96.1
>
>
> 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.1#6144)
