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

Hadoop QA commented on HBASE-7701:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12567461/trunk-7701_v2.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 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:red}-1 core tests{color}.  The patch failed these unit tests:
                       org.apache.hadoop.hbase.client.TestHTableMultiplexer

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/4280//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/4280//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/4280//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/4280//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/4280//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/4280//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/4280//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/4280//console

This message is automatically generated.
                
> Opening regions on dead server are not reassigned quickly
> ---------------------------------------------------------
>
>                 Key: HBASE-7701
>                 URL: https://issues.apache.org/jira/browse/HBASE-7701
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.96.0
>            Reporter: Sergey Shelukhin
>            Assignee: Jimmy Xiang
>         Attachments: 
> TEST-org.apache.hadoop.hbase.IntegrationTestRebalanceAndKillServersTargeted.xml,
>  trunk-7701_v1.patch, trunk-7701_v2.patch
>
>
> Closed regions are not removed from assignments. I am not sure if it's a 
> general state problem, or just a small bug; for now, one manifestation is 
> that moved region is ignored by SSH of the target server if target server 
> dies before updating ZK.
> {code}
> 2013-01-22 17:59:00,524 DEBUG [IPC Server handler 3 on 50658] 
> master.AssignmentManager(1475): Sent CLOSE to 10.11.2.92,51231,1358906285048 
> for region 
> IntegrationTestRebalanceAndKillServersTargeted,66666660,1358906196709.0200b366bc37c5afd1185f7d487c7dfb.
> 2013-01-22 17:59:00,997 DEBUG 
> [RS_CLOSE_REGION-10.11.2.92,51231,1358906285048-1] 
> handler.CloseRegionHandler(167): set region closed state in zk successfully 
> for region 
> IntegrationTestRebalanceAndKillServersTargeted,66666660,1358906196709.0200b366bc37c5afd1185f7d487c7dfb.
>  sn name: 10.11.2.92,51231,1358906285048
> 2013-01-22 17:59:01,088 INFO  
> [MASTER_CLOSE_REGION-10.11.2.92,50658,1358906192673-0] 
> master.RegionStates(242): Region {NAME => 
> 'IntegrationTestRebalanceAndKillServersTargeted,66666660,1358906196709.0200b366bc37c5afd1185f7d487c7dfb.',
>  STARTKEY => '66666660', ENDKEY => '7333332c', 
> ENCODED => 0200b366bc37c5afd1185f7d487c7dfb,} transitioned from 
> {IntegrationTestRebalanceAndKillServersTargeted,66666660,1358906196709.0200b366bc37c5afd1185f7d487c7dfb.
>  state=CLOSED, ts=1358906341087, server=null} to 
> {IntegrationTestRebalanceAndKillServersTargeted,66666660,1358906196709.0200b366bc37c5afd1185f7d487c7dfb.
>  state=OFFLINE, ts=1358906341088, server=null}
> 2013-01-22 17:59:01,128 INFO  
> [MASTER_CLOSE_REGION-10.11.2.92,50658,1358906192673-0] 
> master.AssignmentManager(1596): Assigning region 
> IntegrationTestRebalanceAndKillServersTargeted,66666660,1358906196709.0200b366bc37c5afd1185f7d487c7dfb.
>  to 10.11.2.92,50661,1358906192942
> ... (50661 didn't update ZK to OPEN, only OPENING)
> 2013-01-22 17:59:06,605 INFO  
> [MASTER_SERVER_OPERATIONS-10.11.2.92,50658,1358906192673-2] 
> handler.ServerShutdownHandler(202): Reassigning 7 region(s) that 
> 10.11.2.92,50661,1358906192942 was carrying (skipping 0 regions(s) that are 
> already in transition)
> 2013-01-22 17:59:06,605 DEBUG 
> [MASTER_SERVER_OPERATIONS-10.11.2.92,50658,1358906192673-2] 
> handler.ServerShutdownHandler(219): Skip assigning region 
> IntegrationTestRebalanceAndKillServersTargeted,66666660,1358906196709.0200b366bc37c5afd1185f7d487c7dfb.
>  because it has been opened in 10.11.2.92,51231,1358906285048
> {code}
> Note the server in the last line - the one that has long closed the region.

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

Reply via email to