You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Joe Pallas (JIRA)" <ji...@apache.org> on 2011/09/06 23:49:10 UTC
[jira] [Created] (HBASE-4333) Client does not check for holes in
.META.
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4333) Client does not check for holes in
.META.
Posted by "Lars Hofhansl (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HBASE-4333) Client does not check for holes in
.META.
Posted by "Joe Pallas (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123032#comment-13123032 ]
Joe Pallas commented on HBASE-4333:
-----------------------------------
Are you satisfied that this is not an issue for scanners? If so, I'm okay with 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
[jira] [Resolved] (HBASE-4333) Client does not check for holes in
.META.
Posted by "Lars Hofhansl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl resolved HBASE-4333.
----------------------------------
Resolution: Fixed
Yeah... Marking as fixed.
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4333) Client does not check for holes in
.META.
Posted by "Jesse Yates (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445131#comment-13445131 ]
Jesse Yates commented on HBASE-4333:
------------------------------------
@lars can we close this then?
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4333) Client does not check for holes in
.META.
Posted by "Lars Hofhansl (Commented) (JIRA)" <ji...@apache.org>.
[ 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