hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-11667) Simplify ClientScanner logic for NSREs.
Date Tue, 05 Aug 2014 04:12:13 GMT

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

Andrew Purtell edited comment on HBASE-11667 at 8/5/14 4:11 AM:
----------------------------------------------------------------

Attached as IntegrationTestBigLinkedListWithRegionMovement, an integration test that extends
ITBLL with a fixed monkey policy that moves a random region of the table very often.


was (Author: apurtell):
Attached as IntegrationTestBigLinkedListWithRegionMovement, an integration test that extends
ITBLL with a fixed monkey policy that moves a random region of the table every second. 

> Simplify ClientScanner logic for NSREs.
> ---------------------------------------
>
>                 Key: HBASE-11667
>                 URL: https://issues.apache.org/jira/browse/HBASE-11667
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>             Fix For: 0.99.0, 2.0.0, 0.94.23, 0.98.6
>
>         Attachments: 11667-0.94.txt, 11667-trunk.txt, HBASE-11667-0.98.patch
>
>
> We ran into an issue with Phoenix where a RegionObserver coprocessor intercepts a scan
and returns an aggregate (in this case a count) with a fake row key. It turns out this does
not work when the {{ClientScanner}} encounters NSREs, as it uses the last key it saw to reset
the scanner to try again (which in this case would be the fake key).
> While this is arguably a rare case and one could also argue that a region observer just
shouldn't do this... While looking at {{ClientScanner}}'s code I found this logic not necessary.
> A NSRE occurred because we contacted a region server with a key that it no longer hosts.
This is the start key, so it is always correct to retry with this same key. That simplifies
the ClientScanner logic and also make this sort of coprocessors possible,



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

Mime
View raw message