[ 
https://issues.apache.org/jira/browse/HBASE-10809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943957#comment-13943957
 ] 

Hadoop QA commented on HBASE-10809:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12636183/hbase-10809-v1.patch
  against trunk revision .
  ATTACHMENT ID: 12636183

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified tests.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines 
longer than 100

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/9076//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/9076//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/9076//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/9076//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/9076//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/9076//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/9076//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/9076//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/9076//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/9076//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/9076//console

This message is automatically generated.

> HBaseAdmin#deleteTable fails when META region happen to move around same time
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-10809
>                 URL: https://issues.apache.org/jira/browse/HBASE-10809
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.98.0, 0.96.1, 0.99.0
>            Reporter: Jeffrey Zhong
>            Assignee: Jeffrey Zhong
>         Attachments: hbase-10809-v1.patch, hbase-10809.patch, 
> hbase-10809.patch
>
>
> The issue is that in the retry loop, we never refetch the latest meta 
> location. So if meta starts to move right after the function get Meta server 
> location, the delete table eventually may fail with 
> {code}org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1 
> is not online{code}
> Below is the stack trace:
> {code}
> 2014-01-31 04:02:41,943|beaver.machine|INFO|Caused by: 
> org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.NotServingRegionException):
>  org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1 is 
> not online
> 2014-01-31 04:02:41,943|beaver.machine|INFO|at 
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2585)
> 2014-01-31 04:02:41,943|beaver.machine|INFO|at 
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3952)
> 2014-01-31 04:02:41,944|beaver.machine|INFO|at 
> org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:2977)
> 2014-01-31 04:02:41,944|beaver.machine|INFO|at 
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26929)
> 2014-01-31 04:02:41,944|beaver.machine|INFO|at 
> org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2175)
> 2014-01-31 04:02:41,944|beaver.machine|INFO|at 
> org.apache.hadoop.hbase.ipc.RpcServer$Handler.run(RpcServer.java:1879)
> 2014-01-31 04:02:41,945|beaver.machine|INFO|
> 2014-01-31 04:02:41,945|beaver.machine|INFO|at 
> org.apache.hadoop.hbase.ipc.RpcClient.call(RpcClient.java:1449)
> 2014-01-31 04:02:41,945|beaver.machine|INFO|at 
> org.apache.hadoop.hbase.ipc.RpcClient.callBlockingMethod(RpcClient.java:1653)
> 2014-01-31 04:02:41,946|beaver.machine|INFO|at 
> org.apache.hadoop.hbase.ipc.RpcClient$BlockingRpcChannelImplementation.callBlockingMethod(RpcClient.java:1711)
> 2014-01-31 04:02:41,946|beaver.machine|INFO|at 
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$BlockingStub.scan(ClientProtos.java:27332)
> 2014-01-31 04:02:41,946|beaver.machine|INFO|at 
> org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:648)
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to