[
https://issues.apache.org/jira/browse/HBASE-9303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748092#comment-13748092
]
Jonathan Hsieh commented on HBASE-9303:
---------------------------------------
Ok, so we have a split parent with the SPLIT marker in the hri in meta. Is
this the hri saved off as part of the snapshot manifest, or is it only in the
meta hri? Is the problem only that the meta entry has SPLIT as an attribute?
Could we have a unit test where we force meta to have the split marker and the
restore?
> Snapshot restore of table which splits after snapshot was taken encounters
> 'Region is not online'
> -------------------------------------------------------------------------------------------------
>
> Key: HBASE-9303
> URL: https://issues.apache.org/jira/browse/HBASE-9303
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.95.2
> Reporter: Ted Yu
> Assignee: Matteo Bertozzi
> Attachments: 9303.shell-output, HBASE-9303-0.94-v0.patch,
> HBASE-9303-0.94-v1.patch, HBASE-9303-trunk-v0.patch,
> HBASE-9303-trunk-v1.patch, hbase-hbase-master-hor15n02.log,
> hbase-hbase-regionserver-hor15n02.log
>
>
> Take snapshot of a table ('tablethree' in the log).
> Put some data in the table and split the table.
> Restore snapshot.
> Table cannot be enabled due to:
> {code}
> Thu Aug 22 19:37:20 UTC 2013,
> org.apache.hadoop.hbase.client.RpcRetryingCaller@47a6ac39,
> org.apache.hadoop.hbase.NotServingRegionException:
> org.apache.hadoop.hbase.NotServingRegionException: Region is not online:
> c32e63d8c8a1a94b68966645b956d86d
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2557)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3921)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:2996)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26847)
> {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
