[jira] [Commented] (HBASE-12377) HBaseAdmin#deleteTable fails when META region is moved around the same timeframe

2014-10-31 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-12377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14191534#comment-14191534
 ] 

Hadoop QA commented on HBASE-12377:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12678417/HBASE-12377.v3-2.0.patch
  against trunk revision .
  ATTACHMENT ID: 12678417

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

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

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

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

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

{color:green}+1 checkstyle{color}.  The applied patch does not increase the 
total number of checkstyle errors

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) 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:red}-1 core tests{color}.  The patch failed these unit tests:
   org.apache.hadoop.hbase.util.TestProcessBasedCluster
  org.apache.hadoop.hbase.mapreduce.TestImportExport

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11536//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11536//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11536//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11536//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11536//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11536//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11536//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11536//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11536//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11536//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11536//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11536//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Checkstyle Errors: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11536//artifact/patchprocess/checkstyle-aggregate.html

  Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11536//console

This message is automatically generated.

 HBaseAdmin#deleteTable fails when META region is moved around the same 
 timeframe
 

 Key: HBASE-12377
 URL: https://issues.apache.org/jira/browse/HBASE-12377
 Project: HBase
  Issue Type: Bug
  Components: Client
Affects Versions: 0.98.4
Reporter: Stephen Yuan Jiang
Assignee: Stephen Yuan Jiang
 Fix For: 2.0.0, 0.98.8, 0.99.2

 Attachments: HBASE-12377.v1-2.0.patch, HBASE-12377.v2-2.0.patch, 
 HBASE-12377.v3-2.0.patch


 This is the same issue that HBASE-10809 tried to address.  The fix of 
 HBASE-10809 refetch the latest meta location in retry-loop.  However, there 
 are 2 problems: (1).  inside the retry loop, there is another try-catch block 
 that would throw the exception before retry can kick in; (2). It looks like 
 that HBaseAdmin::getFirstMetaServerForTable() always tries to get meta data 
 from meta cache, which means if the meta cache is stale and out of date, 
 retries would not solve the problem by fetching from the

[jira] [Commented] (HBASE-12377) HBaseAdmin#deleteTable fails when META region is moved around the same timeframe

2014-10-31 Thread Enis Soztutar (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-12377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14192283#comment-14192283
 ] 

Enis Soztutar commented on HBASE-12377:
---

The tests does not seem related. I've run TestProcessBasedCluster, 
TestImportExport again to make sure. 

I've committed this to branch-1+. Thanks Stephen for your first patch, and 
bearing with the reviews! 

 HBaseAdmin#deleteTable fails when META region is moved around the same 
 timeframe
 

 Key: HBASE-12377
 URL: https://issues.apache.org/jira/browse/HBASE-12377
 Project: HBase
  Issue Type: Bug
  Components: Client
Affects Versions: 0.98.4
Reporter: Stephen Yuan Jiang
Assignee: Stephen Yuan Jiang
 Fix For: 2.0.0, 0.99.2

 Attachments: HBASE-12377.v1-2.0.patch, HBASE-12377.v2-2.0.patch, 
 HBASE-12377.v3-2.0.patch


 This is the same issue that HBASE-10809 tried to address.  The fix of 
 HBASE-10809 refetch the latest meta location in retry-loop.  However, there 
 are 2 problems: (1).  inside the retry loop, there is another try-catch block 
 that would throw the exception before retry can kick in; (2). It looks like 
 that HBaseAdmin::getFirstMetaServerForTable() always tries to get meta data 
 from meta cache, which means if the meta cache is stale and out of date, 
 retries would not solve the problem by fetching from the stale meta cache.
 Here is the call stack of the issue:
 {noformat}
 2014-10-27 
 10:11:58,495|beaver.machine|INFO|18218|140065036261120|MainThread|org.apache.hadoop.hbase.NotServingRegionException:
  org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1 is 
 not online on ip-172-31-0-48.ec2.internal,60020,1414403435009
 2014-10-27 
 10:11:58,496|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2774)
 2014-10-27 
 10:11:58,496|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:4257)
 2014-10-27 
 10:11:58,497|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:3156)
 2014-10-27 
 10:11:58,497|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29994)
 2014-10-27 
 10:11:58,498|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2078)
 2014-10-27 
 10:11:58,498|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 java.lang.Thread.run(Thread.java:745)
 2014-10-27 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|
 2014-10-27 
 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 sun.reflect.GeneratedConstructorAccessor12.newInstance(Unknown Source)
 2014-10-27 
 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 2014-10-27 
 10:11:58,501|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 java.lang.reflect.Constructor.newInstance(Constructor.java:526)
 2014-10-27 
 10:11:58,501|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106)
 2014-10-27 
 10:11:58,502|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:95)
 2014-10-27 
 10:11:58,502|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.protobuf.ProtobufUtil.getRemoteException(ProtobufUtil.java:306)
 2014-10-27 
 10:11:58,502|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:699)
 2014-10-27 
 10:11:58,503|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:654)
 2014-10-27 
 10:11:58,503|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.IntegrationTestManyRegions.tearDown(IntegrationTestManyRegions.java:99)
 {noformat}
 The META

[jira] [Commented] (HBASE-12377) HBaseAdmin#deleteTable fails when META region is moved around the same timeframe

2014-10-31 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-12377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14192431#comment-14192431
 ] 

Hudson commented on HBASE-12377:


ABORTED: Integrated in HBase-TRUNK #5732 (See 
[https://builds.apache.org/job/HBase-TRUNK/5732/])
HBASE-12377 HBaseAdmin#deleteTable fails when META region is moved around the 
same timeframe (Stephen Yuan Jiang) (enis: rev 
2d1cfc14f253bbb1aad9be049b6492ead17bc9af)
* hbase-client/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java


 HBaseAdmin#deleteTable fails when META region is moved around the same 
 timeframe
 

 Key: HBASE-12377
 URL: https://issues.apache.org/jira/browse/HBASE-12377
 Project: HBase
  Issue Type: Bug
  Components: Client
Affects Versions: 0.98.4
Reporter: Stephen Yuan Jiang
Assignee: Stephen Yuan Jiang
 Fix For: 2.0.0, 0.99.2

 Attachments: HBASE-12377.v1-2.0.patch, HBASE-12377.v2-2.0.patch, 
 HBASE-12377.v3-2.0.patch


 This is the same issue that HBASE-10809 tried to address.  The fix of 
 HBASE-10809 refetch the latest meta location in retry-loop.  However, there 
 are 2 problems: (1).  inside the retry loop, there is another try-catch block 
 that would throw the exception before retry can kick in; (2). It looks like 
 that HBaseAdmin::getFirstMetaServerForTable() always tries to get meta data 
 from meta cache, which means if the meta cache is stale and out of date, 
 retries would not solve the problem by fetching from the stale meta cache.
 Here is the call stack of the issue:
 {noformat}
 2014-10-27 
 10:11:58,495|beaver.machine|INFO|18218|140065036261120|MainThread|org.apache.hadoop.hbase.NotServingRegionException:
  org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1 is 
 not online on ip-172-31-0-48.ec2.internal,60020,1414403435009
 2014-10-27 
 10:11:58,496|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2774)
 2014-10-27 
 10:11:58,496|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:4257)
 2014-10-27 
 10:11:58,497|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:3156)
 2014-10-27 
 10:11:58,497|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29994)
 2014-10-27 
 10:11:58,498|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2078)
 2014-10-27 
 10:11:58,498|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 java.lang.Thread.run(Thread.java:745)
 2014-10-27 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|
 2014-10-27 
 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 sun.reflect.GeneratedConstructorAccessor12.newInstance(Unknown Source)
 2014-10-27 
 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 2014-10-27 
 10:11:58,501|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 java.lang.reflect.Constructor.newInstance(Constructor.java:526)
 2014-10-27 
 10:11:58,501|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106)
 2014-10-27 
 10:11:58,502|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:95)
 2014-10-27 
 10:11:58,502|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.protobuf.ProtobufUtil.getRemoteException(ProtobufUtil.java:306)
 2014-10-27 
 10:11:58,502|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:699)
 2014-10-27 
 10:11:58,503|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:654)
 2014-10-27 
 10:11:58,503|beaver.machine|INFO|18218|140065036261120|MainThread|at

[jira] [Commented] (HBASE-12377) HBaseAdmin#deleteTable fails when META region is moved around the same timeframe

2014-10-31 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-12377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14192432#comment-14192432
 ] 

Hudson commented on HBASE-12377:


ABORTED: Integrated in HBase-1.0 #401 (See 
[https://builds.apache.org/job/HBase-1.0/401/])
HBASE-12377 HBaseAdmin#deleteTable fails when META region is moved around the 
same timeframe (Stephen Yuan Jiang) (enis: rev 
8938aba4e265dd4d94515312df2a9ebe63ab544f)
* hbase-client/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java


 HBaseAdmin#deleteTable fails when META region is moved around the same 
 timeframe
 

 Key: HBASE-12377
 URL: https://issues.apache.org/jira/browse/HBASE-12377
 Project: HBase
  Issue Type: Bug
  Components: Client
Affects Versions: 0.98.4
Reporter: Stephen Yuan Jiang
Assignee: Stephen Yuan Jiang
 Fix For: 2.0.0, 0.99.2

 Attachments: HBASE-12377.v1-2.0.patch, HBASE-12377.v2-2.0.patch, 
 HBASE-12377.v3-2.0.patch


 This is the same issue that HBASE-10809 tried to address.  The fix of 
 HBASE-10809 refetch the latest meta location in retry-loop.  However, there 
 are 2 problems: (1).  inside the retry loop, there is another try-catch block 
 that would throw the exception before retry can kick in; (2). It looks like 
 that HBaseAdmin::getFirstMetaServerForTable() always tries to get meta data 
 from meta cache, which means if the meta cache is stale and out of date, 
 retries would not solve the problem by fetching from the stale meta cache.
 Here is the call stack of the issue:
 {noformat}
 2014-10-27 
 10:11:58,495|beaver.machine|INFO|18218|140065036261120|MainThread|org.apache.hadoop.hbase.NotServingRegionException:
  org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1 is 
 not online on ip-172-31-0-48.ec2.internal,60020,1414403435009
 2014-10-27 
 10:11:58,496|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2774)
 2014-10-27 
 10:11:58,496|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:4257)
 2014-10-27 
 10:11:58,497|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:3156)
 2014-10-27 
 10:11:58,497|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29994)
 2014-10-27 
 10:11:58,498|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2078)
 2014-10-27 
 10:11:58,498|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 java.lang.Thread.run(Thread.java:745)
 2014-10-27 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|
 2014-10-27 
 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 sun.reflect.GeneratedConstructorAccessor12.newInstance(Unknown Source)
 2014-10-27 
 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 2014-10-27 
 10:11:58,501|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 java.lang.reflect.Constructor.newInstance(Constructor.java:526)
 2014-10-27 
 10:11:58,501|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106)
 2014-10-27 
 10:11:58,502|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:95)
 2014-10-27 
 10:11:58,502|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.protobuf.ProtobufUtil.getRemoteException(ProtobufUtil.java:306)
 2014-10-27 
 10:11:58,502|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:699)
 2014-10-27 
 10:11:58,503|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:654)
 2014-10-27 
 10:11:58,503|beaver.machine|INFO|18218|140065036261120|MainThread|at

[jira] [Commented] (HBASE-12377) HBaseAdmin#deleteTable fails when META region is moved around the same timeframe

2014-10-30 Thread Enis Soztutar (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-12377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14191035#comment-14191035
 ] 

Enis Soztutar commented on HBASE-12377:
---

Can we change this to be a private method, and remove the corresponding 
interface in Admin. Having getTableDescriptor() which throws 
TableNotFoundException, and this new method which returns null instead will be 
confusing to users. 
{code}
+  public HTableDescriptor getTableDescriptorByTableName(TableName tableName)
{code}

Other than that looks good. 

 HBaseAdmin#deleteTable fails when META region is moved around the same 
 timeframe
 

 Key: HBASE-12377
 URL: https://issues.apache.org/jira/browse/HBASE-12377
 Project: HBase
  Issue Type: Bug
  Components: Client
Affects Versions: 0.98.4
Reporter: Stephen Yuan Jiang
Assignee: Stephen Yuan Jiang
 Fix For: 2.0.0, 0.98.8, 0.99.2

 Attachments: HBASE-12377.v1-2.0.patch, HBASE-12377.v2-2.0.patch


 This is the same issue that HBASE-10809 tried to address.  The fix of 
 HBASE-10809 refetch the latest meta location in retry-loop.  However, there 
 are 2 problems: (1).  inside the retry loop, there is another try-catch block 
 that would throw the exception before retry can kick in; (2). It looks like 
 that HBaseAdmin::getFirstMetaServerForTable() always tries to get meta data 
 from meta cache, which means if the meta cache is stale and out of date, 
 retries would not solve the problem by fetching from the stale meta cache.
 Here is the call stack of the issue:
 {noformat}
 2014-10-27 
 10:11:58,495|beaver.machine|INFO|18218|140065036261120|MainThread|org.apache.hadoop.hbase.NotServingRegionException:
  org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1 is 
 not online on ip-172-31-0-48.ec2.internal,60020,1414403435009
 2014-10-27 
 10:11:58,496|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2774)
 2014-10-27 
 10:11:58,496|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:4257)
 2014-10-27 
 10:11:58,497|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:3156)
 2014-10-27 
 10:11:58,497|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29994)
 2014-10-27 
 10:11:58,498|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2078)
 2014-10-27 
 10:11:58,498|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 java.lang.Thread.run(Thread.java:745)
 2014-10-27 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|
 2014-10-27 
 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 sun.reflect.GeneratedConstructorAccessor12.newInstance(Unknown Source)
 2014-10-27 
 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 2014-10-27 
 10:11:58,501|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 java.lang.reflect.Constructor.newInstance(Constructor.java:526)
 2014-10-27 
 10:11:58,501|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106)
 2014-10-27 
 10:11:58,502|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:95)
 2014-10-27 
 10:11:58,502|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.protobuf.ProtobufUtil.getRemoteException(ProtobufUtil.java:306)
 2014-10-27 
 10:11:58,502|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:699)
 2014-10-27 
 10:11:58,503|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:654)
 2014-10-27

[jira] [Commented] (HBASE-12377) HBaseAdmin#deleteTable fails when META region is moved around the same timeframe

2014-10-30 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-12377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14191047#comment-14191047
 ] 

Hadoop QA commented on HBASE-12377:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12678322/HBASE-12377.v2-2.0.patch
  against trunk revision .
  ATTACHMENT ID: 12678322

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

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

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

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

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

{color:green}+1 checkstyle{color}.  The applied patch does not increase the 
total number of checkstyle errors

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) 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:red}-1 core tests{color}.  The patch failed these unit tests:
   
org.apache.hadoop.hbase.mapreduce.TestTableSnapshotInputFormat
  org.apache.hadoop.hbase.coprocessor.TestCoprocessorHConnection

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11527//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11527//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11527//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11527//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11527//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11527//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11527//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11527//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11527//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11527//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11527//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11527//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Checkstyle Errors: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11527//artifact/patchprocess/checkstyle-aggregate.html

  Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11527//console

This message is automatically generated.

 HBaseAdmin#deleteTable fails when META region is moved around the same 
 timeframe
 

 Key: HBASE-12377
 URL: https://issues.apache.org/jira/browse/HBASE-12377
 Project: HBase
  Issue Type: Bug
  Components: Client
Affects Versions: 0.98.4
Reporter: Stephen Yuan Jiang
Assignee: Stephen Yuan Jiang
 Fix For: 2.0.0, 0.98.8, 0.99.2

 Attachments: HBASE-12377.v1-2.0.patch, HBASE-12377.v2-2.0.patch


 This is the same issue that HBASE-10809 tried to address.  The fix of 
 HBASE-10809 refetch the latest meta location in retry-loop.  However, there 
 are 2 problems: (1).  inside the retry loop, there is another try-catch block 
 that would throw the exception before retry can kick in; (2). It looks like 
 that HBaseAdmin::getFirstMetaServerForTable() always tries to get meta data 
 from meta cache, which means if the meta cache is stale and out of date, 
 retries would not solve the problem by fetching from the stale

[jira] [Commented] (HBASE-12377) HBaseAdmin#deleteTable fails when META region is moved around the same timeframe

2014-10-29 Thread Enis Soztutar (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-12377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14189017#comment-14189017
 ] 

Enis Soztutar commented on HBASE-12377:
---

I think HBASE-12072 is related since it unifies some paths so that we are using 
the regular rpc retrying mechanism instead of custom build ones inside 
HBaseAdmin. 

For this issue, the problem is that HBaseAdmin.deleteTable() does not use the 
regular scan rpc code (which handles retrying / meta cache, etc correctly) but 
instead does reinvent the stuff in a broken way. 

Another issue with this is that all this logic is in client side vs it should 
have been in the master side, but that is a different and much more involved 
issue.   

Can we do the patch so that it uses MetaReader or MetaScanner to obtain the 
list of regions for the table in the retry loop? 

 HBaseAdmin#deleteTable fails when META region is moved around the same 
 timeframe
 

 Key: HBASE-12377
 URL: https://issues.apache.org/jira/browse/HBASE-12377
 Project: HBase
  Issue Type: Bug
  Components: Client
Affects Versions: 0.98.4
Reporter: Stephen Yuan Jiang
Assignee: Stephen Yuan Jiang
 Fix For: 2.0.0, 0.98.8, 0.99.2


 This is the same issue that HBASE-10809 tried to address.  The fix of 
 HBASE-10809 refetch the latest meta location in retry-loop.  However, there 
 are 2 problems: (1).  inside the retry loop, there is another try-catch block 
 that would throw the exception before retry can kick in; (2). It looks like 
 that HBaseAdmin::getFirstMetaServerForTable() always tries to get meta data 
 from meta cache, which means if the meta cache is stale and out of date, 
 retries would not solve the problem by fetch the right data.
 Here is the call stack of the issue:
 {noformat}
 2014-10-27 
 10:11:58,495|beaver.machine|INFO|18218|140065036261120|MainThread|org.apache.hadoop.hbase.NotServingRegionException:
  org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1 is 
 not online on ip-172-31-0-48.ec2.internal,60020,1414403435009
 2014-10-27 
 10:11:58,496|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2774)
 2014-10-27 
 10:11:58,496|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:4257)
 2014-10-27 
 10:11:58,497|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:3156)
 2014-10-27 
 10:11:58,497|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29994)
 2014-10-27 
 10:11:58,498|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2078)
 2014-10-27 
 10:11:58,498|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 java.lang.Thread.run(Thread.java:745)
 2014-10-27 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|
 2014-10-27 
 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 sun.reflect.GeneratedConstructorAccessor12.newInstance(Unknown Source)
 2014-10-27 
 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 2014-10-27 
 10:11:58,501|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 java.lang.reflect.Constructor.newInstance(Constructor.java:526)
 2014-10-27 
 10:11:58,501|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106)
 2014-10-27 
 10:11:58,502|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:95)
 2014-10-27 
 10:11:58,502|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.protobuf.ProtobufUtil.getRemoteException(ProtobufUtil.java:306)
 2014-10-27 
 10:11:58,502|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:699)
 2014-10-27

[jira] [Commented] (HBASE-12377) HBaseAdmin#deleteTable fails when META region is moved around the same timeframe

2014-10-29 Thread Ted Yu (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-12377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14189296#comment-14189296
 ] 

Ted Yu commented on HBASE-12377:


lgtm

 HBaseAdmin#deleteTable fails when META region is moved around the same 
 timeframe
 

 Key: HBASE-12377
 URL: https://issues.apache.org/jira/browse/HBASE-12377
 Project: HBase
  Issue Type: Bug
  Components: Client
Affects Versions: 0.98.4
Reporter: Stephen Yuan Jiang
Assignee: Stephen Yuan Jiang
 Fix For: 2.0.0, 0.98.8, 0.99.2

 Attachments: HBASE-12377.v1-2.0.patch


 This is the same issue that HBASE-10809 tried to address.  The fix of 
 HBASE-10809 refetch the latest meta location in retry-loop.  However, there 
 are 2 problems: (1).  inside the retry loop, there is another try-catch block 
 that would throw the exception before retry can kick in; (2). It looks like 
 that HBaseAdmin::getFirstMetaServerForTable() always tries to get meta data 
 from meta cache, which means if the meta cache is stale and out of date, 
 retries would not solve the problem by fetching from the stale meta cache.
 Here is the call stack of the issue:
 {noformat}
 2014-10-27 
 10:11:58,495|beaver.machine|INFO|18218|140065036261120|MainThread|org.apache.hadoop.hbase.NotServingRegionException:
  org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1 is 
 not online on ip-172-31-0-48.ec2.internal,60020,1414403435009
 2014-10-27 
 10:11:58,496|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2774)
 2014-10-27 
 10:11:58,496|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:4257)
 2014-10-27 
 10:11:58,497|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:3156)
 2014-10-27 
 10:11:58,497|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29994)
 2014-10-27 
 10:11:58,498|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2078)
 2014-10-27 
 10:11:58,498|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 java.lang.Thread.run(Thread.java:745)
 2014-10-27 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|
 2014-10-27 
 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 sun.reflect.GeneratedConstructorAccessor12.newInstance(Unknown Source)
 2014-10-27 
 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 2014-10-27 
 10:11:58,501|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 java.lang.reflect.Constructor.newInstance(Constructor.java:526)
 2014-10-27 
 10:11:58,501|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106)
 2014-10-27 
 10:11:58,502|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:95)
 2014-10-27 
 10:11:58,502|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.protobuf.ProtobufUtil.getRemoteException(ProtobufUtil.java:306)
 2014-10-27 
 10:11:58,502|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:699)
 2014-10-27 
 10:11:58,503|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java:654)
 2014-10-27 
 10:11:58,503|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.IntegrationTestManyRegions.tearDown(IntegrationTestManyRegions.java:99)
 {noformat}
 The META region was Online in RS1 when the delete table starts, it was moved 
 to RS2 during the delete table operation.  And the problem appears.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HBASE-12377) HBaseAdmin#deleteTable fails when META region is moved around the same timeframe

2014-10-29 Thread Enis Soztutar (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-12377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14189381#comment-14189381
 ] 

Enis Soztutar commented on HBASE-12377:
---

This looks good. While we are at it, can we do fix the below code for doing a 
custom master rpc as well. Smt like this: 
{code}
-  tableExists = false;
-  GetTableDescriptorsResponse htds;
-  MasterKeepAliveConnection master = 
connection.getKeepAliveMasterService();
-  try {
-GetTableDescriptorsRequest req =
-  RequestConverter.buildGetTableDescriptorsRequest(tableName);
-htds = master.getTableDescriptors(null, req);
-  } catch (ServiceException se) {
-throw ProtobufUtil.getRemoteException(se);
-  } finally {
-master.close();
-  }
-  tableExists = !htds.getTableSchemaList().isEmpty();
-  if (!tableExists) {
+  HTableDescriptor htd =
+  executeCallable(new 
MasterCallableHTableDescriptor(getConnection()) {
+@Override
+public HTableDescriptor call() throws ServiceException {
+  GetTableDescriptorsRequest req =
+  
RequestConverter.buildGetTableDescriptorsRequest(tableName);
+  GetTableDescriptorsResponse htds = 
master.getTableDescriptors(null, req);
+  if (!htds.getTableSchemaList().isEmpty()) {
+return 
HTableDescriptor.convert(htds.getTableSchemaList().get(0));
+  }
+  return null;
+}
+  });
+  if (htd == null) {
{code}



 HBaseAdmin#deleteTable fails when META region is moved around the same 
 timeframe
 

 Key: HBASE-12377
 URL: https://issues.apache.org/jira/browse/HBASE-12377
 Project: HBase
  Issue Type: Bug
  Components: Client
Affects Versions: 0.98.4
Reporter: Stephen Yuan Jiang
Assignee: Stephen Yuan Jiang
 Fix For: 2.0.0, 0.98.8, 0.99.2

 Attachments: HBASE-12377.v1-2.0.patch


 This is the same issue that HBASE-10809 tried to address.  The fix of 
 HBASE-10809 refetch the latest meta location in retry-loop.  However, there 
 are 2 problems: (1).  inside the retry loop, there is another try-catch block 
 that would throw the exception before retry can kick in; (2). It looks like 
 that HBaseAdmin::getFirstMetaServerForTable() always tries to get meta data 
 from meta cache, which means if the meta cache is stale and out of date, 
 retries would not solve the problem by fetching from the stale meta cache.
 Here is the call stack of the issue:
 {noformat}
 2014-10-27 
 10:11:58,495|beaver.machine|INFO|18218|140065036261120|MainThread|org.apache.hadoop.hbase.NotServingRegionException:
  org.apache.hadoop.hbase.NotServingRegionException: Region hbase:meta,,1 is 
 not online on ip-172-31-0-48.ec2.internal,60020,1414403435009
 2014-10-27 
 10:11:58,496|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2774)
 2014-10-27 
 10:11:58,496|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:4257)
 2014-10-27 
 10:11:58,497|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:3156)
 2014-10-27 
 10:11:58,497|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29994)
 2014-10-27 
 10:11:58,498|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2078)
 2014-10-27 
 10:11:58,498|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
 2014-10-27 
 10:11:58,499|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 java.lang.Thread.run(Thread.java:745)
 2014-10-27 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|
 2014-10-27 
 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|at 
 sun.reflect.GeneratedConstructorAccessor12.newInstance(Unknown Source)
 2014-10-27 
 10:11:58,500|beaver.machine|INFO|18218|140065036261120|MainThread|at

[jira] [Commented] (HBASE-12377) HBaseAdmin#deleteTable fails when META region is moved around the same timeframe

2014-10-29 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-12377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14189441#comment-14189441
 ] 

Hadoop QA commented on HBASE-12377:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12678060/HBASE-12377.v1-2.0.patch
  against trunk revision .
  ATTACHMENT ID: 12678060

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

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

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

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

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

{color:green}+1 checkstyle{color}.  The applied patch does not increase the 
total number of checkstyle errors

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) 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 .

 {color:red}-1 core zombie tests{color}.  There are 1 zombie test(s):   
at 
org.apache.ambari.server.upgrade.UpgradeTest.testUpgradedSchema(UpgradeTest.java:107)
at 
org.apache.ambari.server.upgrade.UpgradeTest.testUpgrade(UpgradeTest.java:90)

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11510//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11510//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11510//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11510//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11510//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11510//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11510//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11510//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11510//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11510//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11510//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11510//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Checkstyle Errors: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11510//artifact/patchprocess/checkstyle-aggregate.html

  Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/11510//console

This message is automatically generated.

 HBaseAdmin#deleteTable fails when META region is moved around the same 
 timeframe
 

 Key: HBASE-12377
 URL: https://issues.apache.org/jira/browse/HBASE-12377
 Project: HBase
  Issue Type: Bug
  Components: Client
Affects Versions: 0.98.4
Reporter: Stephen Yuan Jiang
Assignee: Stephen Yuan Jiang
 Fix For: 2.0.0, 0.98.8, 0.99.2

 Attachments: HBASE-12377.v1-2.0.patch


 This is the same issue that HBASE-10809 tried to address.  The fix of 
 HBASE-10809 refetch the latest meta location in retry-loop.  However, there 
 are 2 problems: (1).  inside the retry loop, there is another try-catch block 
 that would throw the exception before retry can kick in; (2). It looks like 
 that HBaseAdmin::getFirstMetaServerForTable() always tries to get meta data 
 from meta cache, which means if the meta cache is stale and out of