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

Hadoop QA commented on HBASE-13337:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12708834/HBASE-13337.patch
  against master branch at commit 485800830a58da1af31beaac859d99b56d823f99.
  ATTACHMENT ID: 12708834

    {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 hadoop versions{color}. The patch compiles with all 
supported hadoop versions (2.4.1 2.5.2 2.6.0)

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

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

    {color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 4 
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:red}-1 release audit{color}.  The applied patch generated 1 release 
audit warnings (more than the master's current 0 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:
     

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/13529//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/13529//artifact/patchprocess/patchReleaseAuditWarnings.txt
Release Findbugs (version 2.0.3)        warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/13529//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors: 
https://builds.apache.org/job/PreCommit-HBASE-Build/13529//artifact/patchprocess/checkstyle-aggregate.html

  Javadoc warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/13529//artifact/patchprocess/patchJavadocWarnings.txt
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/13529//console

This message is automatically generated.

> Table regions are not assigning back, after restarting all regionservers at 
> once.
> ---------------------------------------------------------------------------------
>
>                 Key: HBASE-13337
>                 URL: https://issues.apache.org/jira/browse/HBASE-13337
>             Project: HBase
>          Issue Type: Bug
>          Components: Region Assignment
>    Affects Versions: 2.0.0
>            Reporter: Y. SREENIVASULU REDDY
>            Assignee: Jimmy Xiang
>            Priority: Blocker
>             Fix For: 2.0.0
>
>         Attachments: HBASE-13337.patch
>
>
> Regions of the table are continouly in state=FAILED_CLOSE.
> {noformat}
> Region                                        State                           
>                                                                               
>                                                   RIT time (ms)
> 8f62e819b356736053e06240f7f7c6fd      
> t1,55555555,1427362431330.8f62e819b356736053e06240f7f7c6fd. 
> state=FAILED_CLOSE, ts=Thu Mar 26 15:05:36 IST 2015 (113s ago), 
> server=VM1,16040,1427362531818      113929
> caf59209ae65ea80fca6bdc6996a7d68      
> t1,dddddddd,1427362431330.caf59209ae65ea80fca6bdc6996a7d68. 
> state=FAILED_CLOSE, ts=Thu Mar 26 15:05:36 IST 2015 (113s ago), 
> server=VM2,16040,1427362533691      113929
> db52a74988f71e5cf257bbabf31f26f3      
> t1,44444444,1427362431330.db52a74988f71e5cf257bbabf31f26f3. 
> state=FAILED_CLOSE, ts=Thu Mar 26 15:05:36 IST 2015 (113s ago), 
> server=VM3,16040,1427362533691      113920
> 43f3a65b9f9ff283f598c5450feab1f8      
> t1,88888888,1427362431330.43f3a65b9f9ff283f598c5450feab1f8. 
> state=FAILED_CLOSE, ts=Thu Mar 26 15:05:36 IST 2015 (113s ago), 
> server=VM1,16040,1427362531818      113920
> {noformat}
> *Steps to reproduce:*
> 1. Start HBase cluster with more than one regionserver.
> 2. Create a table with precreated regions. (lets say 15 regions)
> 3. Make sure the regions are well balanced.
> 4. Restart all the Regionservers process at once across the cluster, except 
> HMaster process
> 5. After restarting the Regionservers, successfully will connect to the 
> HMaster.
> *Bug:*
> But no regions are assigning back to the Regionservers.
> *Master log shows as follows:*
> {noformat}
> 2015-03-26 15:05:36,201 INFO  [VM2,16020,1427362216887-GeneralBulkAssigner-0] 
> master.RegionStates: Transition {8f62e819b356736053e06240f7f7c6fd 
> state=OFFLINE, ts=1427362536106, server=VM2,16040,1427362242602} to 
> {8f62e819b356736053e06240f7f7c6fd state=PENDING_OPEN, ts=1427362536201, 
> server=VM1,16040,1427362531818}
> 2015-03-26 15:05:36,202 INFO  [VM2,16020,1427362216887-GeneralBulkAssigner-0] 
> master.RegionStateStore: Updating row 
> t1,55555555,1427362431330.8f62e819b356736053e06240f7f7c6fd. with 
> state=PENDING_OPEN&sn=VM1,16040,1427362531818
> 2015-03-26 15:05:36,244 DEBUG [VM2,16020,1427362216887-GeneralBulkAssigner-0] 
> master.AssignmentManager: Force region state offline 
> {8f62e819b356736053e06240f7f7c6fd state=PENDING_OPEN, ts=1427362536201, 
> server=VM1,16040,1427362531818}
> 2015-03-26 15:05:36,244 INFO  [VM2,16020,1427362216887-GeneralBulkAssigner-0] 
> master.RegionStates: Transition {8f62e819b356736053e06240f7f7c6fd 
> state=PENDING_OPEN, ts=1427362536201, server=VM1,16040,1427362531818} to 
> {8f62e819b356736053e06240f7f7c6fd state=PENDING_CLOSE, ts=1427362536244, 
> server=VM1,16040,1427362531818}
> 2015-03-26 15:05:36,244 INFO  [VM2,16020,1427362216887-GeneralBulkAssigner-0] 
> master.RegionStateStore: Updating row 
> t1,55555555,1427362431330.8f62e819b356736053e06240f7f7c6fd. with 
> state=PENDING_CLOSE
> 2015-03-26 15:05:36,248 INFO  [VM2,16020,1427362216887-GeneralBulkAssigner-0] 
> master.AssignmentManager: Server VM1,16040,1427362531818 returned 
> java.nio.channels.ClosedChannelException for 
> t1,55555555,1427362431330.8f62e819b356736053e06240f7f7c6fd., try=1 of 10
> 2015-03-26 15:05:36,248 INFO  [VM2,16020,1427362216887-GeneralBulkAssigner-0] 
> master.AssignmentManager: Server VM1,16040,1427362531818 returned 
> java.nio.channels.ClosedChannelException for 
> t1,55555555,1427362431330.8f62e819b356736053e06240f7f7c6fd., try=2 of 10
> 2015-03-26 15:05:36,249 INFO  [VM2,16020,1427362216887-GeneralBulkAssigner-0] 
> master.AssignmentManager: Server VM1,16040,1427362531818 returned 
> java.nio.channels.ClosedChannelException for 
> t1,55555555,1427362431330.8f62e819b356736053e06240f7f7c6fd., try=3 of 10
> 2015-03-26 15:05:36,249 INFO  [VM2,16020,1427362216887-GeneralBulkAssigner-0] 
> master.AssignmentManager: Server VM1,16040,1427362531818 returned 
> java.nio.channels.ClosedChannelException for 
> t1,55555555,1427362431330.8f62e819b356736053e06240f7f7c6fd., try=4 of 10
> 2015-03-26 15:05:36,249 INFO  [VM2,16020,1427362216887-GeneralBulkAssigner-0] 
> master.AssignmentManager: Server VM1,16040,1427362531818 returned 
> java.nio.channels.ClosedChannelException for 
> t1,55555555,1427362431330.8f62e819b356736053e06240f7f7c6fd., try=5 of 10
> 2015-03-26 15:05:36,250 INFO  [VM2,16020,1427362216887-GeneralBulkAssigner-0] 
> master.AssignmentManager: Server VM1,16040,1427362531818 returned 
> java.nio.channels.ClosedChannelException for 
> t1,55555555,1427362431330.8f62e819b356736053e06240f7f7c6fd., try=6 of 10
> 2015-03-26 15:05:36,250 INFO  [VM2,16020,1427362216887-GeneralBulkAssigner-0] 
> master.AssignmentManager: Server VM1,16040,1427362531818 returned 
> java.nio.channels.ClosedChannelException for 
> t1,55555555,1427362431330.8f62e819b356736053e06240f7f7c6fd., try=7 of 10
> 2015-03-26 15:05:36,250 INFO  [VM2,16020,1427362216887-GeneralBulkAssigner-0] 
> master.AssignmentManager: Server VM1,16040,1427362531818 returned 
> java.nio.channels.ClosedChannelException for 
> t1,55555555,1427362431330.8f62e819b356736053e06240f7f7c6fd., try=8 of 10
> 2015-03-26 15:05:36,251 INFO  [VM2,16020,1427362216887-GeneralBulkAssigner-0] 
> master.AssignmentManager: Server VM1,16040,1427362531818 returned 
> java.nio.channels.ClosedChannelException for 
> t1,55555555,1427362431330.8f62e819b356736053e06240f7f7c6fd., try=9 of 10
> 2015-03-26 15:05:36,251 INFO  [VM2,16020,1427362216887-GeneralBulkAssigner-0] 
> master.AssignmentManager: Server VM1,16040,1427362531818 returned 
> java.nio.channels.ClosedChannelException for 
> t1,55555555,1427362431330.8f62e819b356736053e06240f7f7c6fd., try=10 of 10
> 2015-03-26 15:05:36,251 WARN  [VM2,16020,1427362216887-GeneralBulkAssigner-0] 
> master.RegionStates: Failed to open/close 8f62e819b356736053e06240f7f7c6fd on 
> VM1,16040,1427362531818, set to FAILED_CLOSE
> 2015-03-26 15:05:36,251 INFO  [VM2,16020,1427362216887-GeneralBulkAssigner-0] 
> master.RegionStates: Transition {8f62e819b356736053e06240f7f7c6fd 
> state=PENDING_CLOSE, ts=1427362536244, server=VM1,16040,1427362531818} to 
> {8f62e819b356736053e06240f7f7c6fd state=FAILED_CLOSE, ts=1427362536251, 
> server=VM1,16040,1427362531818}
> 2015-03-26 15:05:36,251 INFO  [VM2,16020,1427362216887-GeneralBulkAssigner-0] 
> master.RegionStateStore: Updating row 
> t1,55555555,1427362431330.8f62e819b356736053e06240f7f7c6fd. with 
> state=FAILED_CLOSE
> {noformat}



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

Reply via email to