[
https://issues.apache.org/jira/browse/HBASE-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13639907#comment-13639907
]
Himanshu Vashishtha commented on HBASE-8414:
--------------------------------------------
Looking at the HBaseFsck code. I see that checkMetaRegion is called when fixing
an online cluster. I think it is right to make a blocking call to locate meta
in the method; and in case it is not assigned, ask the master to do a force
assign via fixUnassigned method call. [~jxiang], jon, any suggestions on this.
> Hbck still refers to -ROOT- table to locate .META.
> --------------------------------------------------
>
> Key: HBASE-8414
> URL: https://issues.apache.org/jira/browse/HBASE-8414
> Project: HBase
> Issue Type: Bug
> Components: hbck
> Affects Versions: 0.95.0
> Reporter: Himanshu Vashishtha
>
> In the current ROOT-less trunk, hbck still tries to fix meta by looking its
> location in the .ROOT. table. This happens if there is no .META. assigned
> when hbck is ran.
> HbaseFsck.java:
> {code}
> boolean checkMetaRegion() {
> ...
> HRegionLocation rootLocation = connection.locateRegion(
> HConstants.ROOT_TABLE_NAME, HConstants.EMPTY_START_ROW);
> ...
> }
> {code}
> Running hbck while meta is in transition:
> {code}
> bin/hbase hbck
> Version: 0.95.0-SNAPSHOT
> ERROR: META region or some of its attributes are null.
> ERROR: Fatal error: unable to get root region location. Exiting...
> Summary:
> 2 inconsistencies detected.
> Status: INCONSISTENT
> {code}
--
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
