[
https://issues.apache.org/jira/browse/HBASE-18022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004987#comment-16004987
]
Xiang Li commented on HBASE-18022:
----------------------------------
Refine the error message as
bq. Region of 't1,,1492763727308.a9146e6548fc2eeaca2b2d718db32230.' is expected
in the tabe of 't1', but hbase:meta says it is in the table of 't2'. hbase:meta
might be damaged.
> Refine the error message issued with TableNotFoundException when expected
> table is not the same as the one fetched from meta
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-18022
> URL: https://issues.apache.org/jira/browse/HBASE-18022
> Project: HBase
> Issue Type: Improvement
> Reporter: Xiang Li
> Assignee: Xiang Li
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-18022.master.000.patch
>
>
> Regarding the following error message
> bq. ERROR: java.io.IOException:
> org.apache.hadoop.hbase.TableNotFoundException: Table 'hbase:acl' was not
> found, got: table1.
> It is not clear. Users have no idea what it means and have to check the code
> and find that it is issued by ConnectionImplementation#locateRegionInMeta()
> when the table inputted is not the same as the one fetched from meta.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
