You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2013/08/22 21:59:52 UTC
[jira] [Updated] (HBASE-9303) Snapshot restore of table which
splits after snapshot was taken encounters 'Region is not online'
[ https://issues.apache.org/jira/browse/HBASE-9303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu updated HBASE-9303:
--------------------------
Attachment: hbase-hbase-regionserver-hor15n02.log
hbase-hbase-master-hor15n02.log
Logs files.
Snapshot for tablethree was taken.
When restoring, region c32e63d8c8a1a94b68966645b956d86d couldn't get online.
> 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
> Attachments: 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