[
https://issues.apache.org/jira/browse/HBASE-10786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13939883#comment-13939883
]
Matteo Bertozzi commented on HBASE-10786:
-----------------------------------------
ok, from the title I was thinking at a message that shows every region missing
or new. and not just the first one.
since we have the two list "snapshotRegions" and "regions" you can output
something like
the list of region missing from the snapshot and the regions that are in the
snapshot but no longer in the table.
anyway, I guess that with the patch is already a bit better that what we have
now.
> If snapshot verification fails with 'Regions moved', the message should
> contain the name of region causing the failure
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-10786
> URL: https://issues.apache.org/jira/browse/HBASE-10786
> Project: HBase
> Issue Type: Task
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Minor
> Attachments: 10786-v1.txt
>
>
> I was trying to find cause for test failure in
> https://builds.apache.org/job/PreCommit-HBASE-Build/9036//testReport/org.apache.hadoop.hbase.snapshot/TestSecureExportSnapshot/testExportRetry/
> :
> {code}
> org.apache.hadoop.hbase.snapshot.HBaseSnapshotException:
> org.apache.hadoop.hbase.snapshot.HBaseSnapshotException: Snapshot {
> ss=emptySnaptb0-1395177346656 table=testtb-1395177346656 type=FLUSH } had an
> error. Procedure emptySnaptb0-1395177346656 { waiting=[] done=[] }
> at
> org.apache.hadoop.hbase.master.snapshot.SnapshotManager.isSnapshotDone(SnapshotManager.java:342)
> at
> org.apache.hadoop.hbase.master.HMaster.isSnapshotDone(HMaster.java:3007)
> at
> org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:40494)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2020)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)
> at
> org.apache.hadoop.hbase.ipc.FifoRpcScheduler$1.run(FifoRpcScheduler.java:73)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.apache.hadoop.hbase.snapshot.CorruptedSnapshotException via
> Failed taking snapshot { ss=emptySnaptb0-1395177346656
> table=testtb-1395177346656 type=FLUSH } due to exception:Regions moved during
> the snapshot '{ ss=emptySnaptb0-1395177346656 table=testtb-1395177346656
> type=FLUSH }'. expected=9
> snapshotted=8:org.apache.hadoop.hbase.snapshot.CorruptedSnapshotException:
> Regions moved during the snapshot '{ ss=emptySnaptb0-1395177346656
> table=testtb-1395177346656 type=FLUSH }'. expected=9 snapshotted=8
> at
> org.apache.hadoop.hbase.errorhandling.ForeignExceptionDispatcher.rethrowException(ForeignExceptionDispatcher.java:83)
> at
> org.apache.hadoop.hbase.master.snapshot.TakeSnapshotHandler.rethrowExceptionIfFailed(TakeSnapshotHandler.java:320)
> at
> org.apache.hadoop.hbase.master.snapshot.SnapshotManager.isSnapshotDone(SnapshotManager.java:332)
> ... 11 more
> {code}
> However, it is not clear which region caused the verification to fail.
> I searched for log from balancer but found none.
> The exception message should include region name which caused the
> verification to fail.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
