[
https://issues.apache.org/jira/browse/HBASE-19774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16331762#comment-16331762
]
Sergey Soldatov commented on HBASE-19774:
-----------------------------------------
[~mdrob] That's the interesting part. This incorrect behavior exists for many
releases already. As I already mentioned earlier the exception would be still
TNFE but with a missleading message. In 1.x "A not found, got B". In 2.x that
would be very scary message about corrupted meta. And actually, that was
revealed because of HBASE-19775 when shell received TNFE wrapped by
UncheckedIOException, so it was unable to properly handle it.
> incorrect behavior of locateRegionInMeta
> ----------------------------------------
>
> Key: HBASE-19774
> URL: https://issues.apache.org/jira/browse/HBASE-19774
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.0.0-beta-1
> Reporter: Romil Choksi
> Assignee: Sergey Soldatov
> Priority: Major
> Fix For: 2.0.0-beta-2
>
> Attachments: HBASE-19774-branch-2.patch,
> HBASE-19774-wip-branch-2.patch, HBASE-19774.master.patch
>
>
> When we try to operate with not existing table, in some circumstances we get
> an incorrect report about the not existing table:
> {noformat}
> ERROR: Region of
> 'hbase:namespace,,1510363071508.0d8ddea7654f95130959218e9bc9c89c.' is
> expected in the table of 'nonExistentUsertable', but hbase:meta says it is in
> the table of 'hbase:namespace'. hbase:meta might be damaged.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
