hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4333) Client does not check for holes in .META.
Date Sat, 08 Oct 2011 03:29:29 GMT

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

Lars Hofhansl commented on HBASE-4333:

The standard ClientScanner will do the right thing. I.e. scan until the end of the region
and then use that last key to find the next region. The scan starting at the next region will
then fail/retry.

> Client does not check for holes in .META.
> -----------------------------------------
>                 Key: HBASE-4333
>                 URL: https://issues.apache.org/jira/browse/HBASE-4333
>             Project: HBase
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 0.90.4
>            Reporter: Joe Pallas
> If there is a temporary hole in .META., the client may get the wrong region from HConnection.locateRegion.
 HConnectionManager.HConnectionImplementation.locateRegionInMeta should check the end key
of the region found with getClosestRowBefore, just as it checks the offline status, when it
looks at the region info.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message