[jira] [Commented] (HBASE-9092) OpenRegion could be ignored by mistake

2013-08-01 Thread Hudson (JIRA)

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

Hudson commented on HBASE-9092:
---

SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #647 (See 
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/647/])
HBASE-9092 OpenRegion could be ignored by mistake (jxiang: rev 1509384)
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/RegionStates.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManagerOnCluster.java


> OpenRegion could be ignored by mistake
> --
>
> Key: HBASE-9092
> URL: https://issues.apache.org/jira/browse/HBASE-9092
> Project: HBase
>  Issue Type: Bug
>  Components: Region Assignment
>Reporter: Jimmy Xiang
>Assignee: Jimmy Xiang
>Priority: Minor
> Fix For: 0.98.0, 0.95.2
>
> Attachments: trunk-9092.patch
>
>
> Looked into failed test: 
> http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/721/testReport/
> In this test run, several tests in TestAssignmentManagerOnCluster failed.  
> Most of them timed out because the first failure testOpenFailedUnrecoverable 
> used too much resource in deleting the table.
> http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/721/testReport/org.apache.hadoop.hbase.master/TestAssignmentManagerOnCluster/testOpenFailedUnrecoverable/
> The reason testOpenFailedUnrecoverable failed is that the second openRegion 
> call was ignored since the previous open call was still going on and stayed 
> in OpenRegionHandler#doCleanUpOnFailedOpen for too long (perhaps thread 
> scheduling issue).  The second openRegion call was skipped since the region 
> was still in the middle of opening.  However, the failed_open event was 
> already processed by master.  Therefore the region stuck in transition and 
> the delete table went no where.  It is a similar issue as we ran into before 
> while for that time, the region was closing.

--
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


[jira] [Commented] (HBASE-9092) OpenRegion could be ignored by mistake

2013-08-01 Thread Hudson (JIRA)

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

Hudson commented on HBASE-9092:
---

SUCCESS: Integrated in hbase-0.95-on-hadoop2 #213 (See 
[https://builds.apache.org/job/hbase-0.95-on-hadoop2/213/])
HBASE-9092 OpenRegion could be ignored by mistake (jxiang: rev 1509385)
* 
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
* 
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/RegionStates.java
* 
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManagerOnCluster.java


> OpenRegion could be ignored by mistake
> --
>
> Key: HBASE-9092
> URL: https://issues.apache.org/jira/browse/HBASE-9092
> Project: HBase
>  Issue Type: Bug
>  Components: Region Assignment
>Reporter: Jimmy Xiang
>Assignee: Jimmy Xiang
>Priority: Minor
> Fix For: 0.98.0, 0.95.2
>
> Attachments: trunk-9092.patch
>
>
> Looked into failed test: 
> http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/721/testReport/
> In this test run, several tests in TestAssignmentManagerOnCluster failed.  
> Most of them timed out because the first failure testOpenFailedUnrecoverable 
> used too much resource in deleting the table.
> http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/721/testReport/org.apache.hadoop.hbase.master/TestAssignmentManagerOnCluster/testOpenFailedUnrecoverable/
> The reason testOpenFailedUnrecoverable failed is that the second openRegion 
> call was ignored since the previous open call was still going on and stayed 
> in OpenRegionHandler#doCleanUpOnFailedOpen for too long (perhaps thread 
> scheduling issue).  The second openRegion call was skipped since the region 
> was still in the middle of opening.  However, the failed_open event was 
> already processed by master.  Therefore the region stuck in transition and 
> the delete table went no where.  It is a similar issue as we ran into before 
> while for that time, the region was closing.

--
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


[jira] [Commented] (HBASE-9092) OpenRegion could be ignored by mistake

2013-08-01 Thread Hudson (JIRA)

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

Hudson commented on HBASE-9092:
---

SUCCESS: Integrated in HBase-TRUNK #4330 (See 
[https://builds.apache.org/job/HBase-TRUNK/4330/])
HBASE-9092 OpenRegion could be ignored by mistake (jxiang: rev 1509384)
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/RegionStates.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManagerOnCluster.java


> OpenRegion could be ignored by mistake
> --
>
> Key: HBASE-9092
> URL: https://issues.apache.org/jira/browse/HBASE-9092
> Project: HBase
>  Issue Type: Bug
>  Components: Region Assignment
>Reporter: Jimmy Xiang
>Assignee: Jimmy Xiang
>Priority: Minor
> Fix For: 0.98.0, 0.95.2
>
> Attachments: trunk-9092.patch
>
>
> Looked into failed test: 
> http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/721/testReport/
> In this test run, several tests in TestAssignmentManagerOnCluster failed.  
> Most of them timed out because the first failure testOpenFailedUnrecoverable 
> used too much resource in deleting the table.
> http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/721/testReport/org.apache.hadoop.hbase.master/TestAssignmentManagerOnCluster/testOpenFailedUnrecoverable/
> The reason testOpenFailedUnrecoverable failed is that the second openRegion 
> call was ignored since the previous open call was still going on and stayed 
> in OpenRegionHandler#doCleanUpOnFailedOpen for too long (perhaps thread 
> scheduling issue).  The second openRegion call was skipped since the region 
> was still in the middle of opening.  However, the failed_open event was 
> already processed by master.  Therefore the region stuck in transition and 
> the delete table went no where.  It is a similar issue as we ran into before 
> while for that time, the region was closing.

--
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


[jira] [Commented] (HBASE-9092) OpenRegion could be ignored by mistake

2013-08-01 Thread Hudson (JIRA)

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

Hudson commented on HBASE-9092:
---

SUCCESS: Integrated in hbase-0.95 #394 (See 
[https://builds.apache.org/job/hbase-0.95/394/])
HBASE-9092 OpenRegion could be ignored by mistake (jxiang: rev 1509385)
* 
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
* 
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/RegionStates.java
* 
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManagerOnCluster.java


> OpenRegion could be ignored by mistake
> --
>
> Key: HBASE-9092
> URL: https://issues.apache.org/jira/browse/HBASE-9092
> Project: HBase
>  Issue Type: Bug
>  Components: Region Assignment
>Reporter: Jimmy Xiang
>Assignee: Jimmy Xiang
>Priority: Minor
> Fix For: 0.98.0, 0.95.2
>
> Attachments: trunk-9092.patch
>
>
> Looked into failed test: 
> http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/721/testReport/
> In this test run, several tests in TestAssignmentManagerOnCluster failed.  
> Most of them timed out because the first failure testOpenFailedUnrecoverable 
> used too much resource in deleting the table.
> http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/721/testReport/org.apache.hadoop.hbase.master/TestAssignmentManagerOnCluster/testOpenFailedUnrecoverable/
> The reason testOpenFailedUnrecoverable failed is that the second openRegion 
> call was ignored since the previous open call was still going on and stayed 
> in OpenRegionHandler#doCleanUpOnFailedOpen for too long (perhaps thread 
> scheduling issue).  The second openRegion call was skipped since the region 
> was still in the middle of opening.  However, the failed_open event was 
> already processed by master.  Therefore the region stuck in transition and 
> the delete table went no where.  It is a similar issue as we ran into before 
> while for that time, the region was closing.

--
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


[jira] [Commented] (HBASE-9092) OpenRegion could be ignored by mistake

2013-08-01 Thread stack (JIRA)

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

stack commented on HBASE-9092:
--

+1

I like the call to unassign if FAILED_OPEN before moving on.

> OpenRegion could be ignored by mistake
> --
>
> Key: HBASE-9092
> URL: https://issues.apache.org/jira/browse/HBASE-9092
> Project: HBase
>  Issue Type: Bug
>  Components: Region Assignment
>Reporter: Jimmy Xiang
>Assignee: Jimmy Xiang
>Priority: Minor
> Fix For: 0.98.0, 0.95.2
>
> Attachments: trunk-9092.patch
>
>
> Looked into failed test: 
> http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/721/testReport/
> In this test run, several tests in TestAssignmentManagerOnCluster failed.  
> Most of them timed out because the first failure testOpenFailedUnrecoverable 
> used too much resource in deleting the table.
> http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/721/testReport/org.apache.hadoop.hbase.master/TestAssignmentManagerOnCluster/testOpenFailedUnrecoverable/
> The reason testOpenFailedUnrecoverable failed is that the second openRegion 
> call was ignored since the previous open call was still going on and stayed 
> in OpenRegionHandler#doCleanUpOnFailedOpen for too long (perhaps thread 
> scheduling issue).  The second openRegion call was skipped since the region 
> was still in the middle of opening.  However, the failed_open event was 
> already processed by master.  Therefore the region stuck in transition and 
> the delete table went no where.  It is a similar issue as we ran into before 
> while for that time, the region was closing.

--
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


[jira] [Commented] (HBASE-9092) OpenRegion could be ignored by mistake

2013-07-30 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-9092:
--

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12595080/trunk-9092.patch
  against trunk revision .

{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 hadoop1.0{color}.  The patch compiles against the hadoop 
1.0 profile.

{color:green}+1 hadoop2.0{color}.  The patch compiles against the hadoop 
2.0 profile.

{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/6534//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6534//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6534//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6534//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6534//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6534//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6534//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6534//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6534//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/6534//console

This message is automatically generated.

> OpenRegion could be ignored by mistake
> --
>
> Key: HBASE-9092
> URL: https://issues.apache.org/jira/browse/HBASE-9092
> Project: HBase
>  Issue Type: Bug
>  Components: Region Assignment
>Reporter: Jimmy Xiang
>Assignee: Jimmy Xiang
>Priority: Minor
> Fix For: 0.98.0, 0.95.2
>
> Attachments: trunk-9092.patch
>
>
> Looked into failed test: 
> http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/721/testReport/
> In this test run, several tests in TestAssignmentManagerOnCluster failed.  
> Most of them timed out because the first failure testOpenFailedUnrecoverable 
> used too much resource in deleting the table.
> http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/721/testReport/org.apache.hadoop.hbase.master/TestAssignmentManagerOnCluster/testOpenFailedUnrecoverable/
> The reason testOpenFailedUnrecoverable failed is that the second openRegion 
> call was ignored since the previous open call was still going on and stayed 
> in OpenRegionHandler#doCleanUpOnFailedOpen for too long (perhaps thread 
> scheduling issue).  The second openRegion call was skipped since the region 
> was still in the middle of opening.  However, the failed_open event was 
> already processed by master.  Therefore the region stuck in transition and 
> the delete table went no where.  It is a similar issue as we ran into before 
> while for that time, the region was closing.

--
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


[jira] [Commented] (HBASE-9092) OpenRegion could be ignored by mistake

2013-07-30 Thread stack (JIRA)

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

stack commented on HBASE-9092:
--

Nice digging [~jxiang]

> OpenRegion could be ignored by mistake
> --
>
> Key: HBASE-9092
> URL: https://issues.apache.org/jira/browse/HBASE-9092
> Project: HBase
>  Issue Type: Bug
>  Components: Region Assignment
>Reporter: Jimmy Xiang
>Assignee: Jimmy Xiang
>Priority: Minor
>
> Looked into failed test: 
> http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/721/testReport/
> In this test run, several tests in TestAssignmentManagerOnCluster failed.  
> Most of them timed out because the first failure testOpenFailedUnrecoverable 
> used too much resource in deleting the table.
> http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/721/testReport/org.apache.hadoop.hbase.master/TestAssignmentManagerOnCluster/testOpenFailedUnrecoverable/
> The reason testOpenFailedUnrecoverable failed is that the second openRegion 
> call was ignored since the previous open call was still going on and stayed 
> in OpenRegionHandler#doCleanUpOnFailedOpen for too long (perhaps thread 
> scheduling issue).  The second openRegion call was skipped since the region 
> was still in the middle of opening.  However, the failed_open event was 
> already processed by master.  Therefore the region stuck in transition and 
> the delete table went no where.  It is a similar issue as we ran into before 
> while for that time, the region was closing.

--
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


[jira] [Commented] (HBASE-9092) OpenRegion could be ignored by mistake

2013-07-30 Thread Jimmy Xiang (JIRA)

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

Jimmy Xiang commented on HBASE-9092:


That's the region stuck in transition:

{noformat}
2013-07-30 12:49:30,857 INFO  [RpcServer.handler=2,port=35619] 
regionserver.HRegionServer(3468): Receiving OPEN for the 
region:testOpenFailedUnrecoverable,A,1375188570630.e760841b763bd2e8e453af3b6c7c7b6b.
 , which we are already trying to OPEN - ignoring this new request for this 
region.
{noformat}

> OpenRegion could be ignored by mistake
> --
>
> Key: HBASE-9092
> URL: https://issues.apache.org/jira/browse/HBASE-9092
> Project: HBase
>  Issue Type: Bug
>  Components: Region Assignment
>Reporter: Jimmy Xiang
>Assignee: Jimmy Xiang
>Priority: Minor
>
> Looked into failed test: 
> http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/721/testReport/
> In this test run, several tests in TestAssignmentManagerOnCluster failed.  
> Most of them timed out because the first failure testOpenFailedUnrecoverable 
> used too much resource in deleting the table.
> http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/721/testReport/org.apache.hadoop.hbase.master/TestAssignmentManagerOnCluster/testOpenFailedUnrecoverable/
> The reason testOpenFailedUnrecoverable failed is that the second openRegion 
> call was ignored since the previous open call was still going on and stayed 
> in OpenRegionHandler#doCleanUpOnFailedOpen for too long (perhaps thread 
> scheduling issue).  The second openRegion call was skipped since the region 
> was still in the middle of opening.  However, the failed_open event was 
> already processed by master.  Therefore the region stuck in transition and 
> the delete table went no where.  It is a similar issue as we ran into before 
> while for that time, the region was closing.

--
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