You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (Commented) (JIRA)" <ji...@apache.org> on 2011/10/07 04:24:29 UTC
[jira] [Commented] (HBASE-4333) Client does not check for holes in
.META.
[ https://issues.apache.org/jira/browse/HBASE-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122496#comment-13122496 ]
Lars Hofhansl commented on HBASE-4333:
--------------------------------------
I would prefer to have a log message on the server, rather than silently (from the viewpoint of the server logs) ignoring holes on the client.
With HBASE-4334 in place I propose closing this.
> 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