hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8169) TestMasterFailover#testMasterFailoverWithMockedRITOnDeadRS may fail due to regions randomly assigned to a RS
Date Thu, 04 Apr 2013 23:28:15 GMT

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

Hadoop QA commented on HBASE-8169:

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  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 6 new or modified

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

This message is automatically generated.
> TestMasterFailover#testMasterFailoverWithMockedRITOnDeadRS may fail due to regions randomly
assigned to a RS
> ------------------------------------------------------------------------------------------------------------
>                 Key: HBASE-8169
>                 URL: https://issues.apache.org/jira/browse/HBASE-8169
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.98.0, 0.94.7
>            Reporter: Jeffrey Zhong
>            Assignee: Jeffrey Zhong
>            Priority: Minor
>             Fix For: 0.98.0, 0.94.7
>         Attachments: hbase-8169_0.94_rebased.patch, hbase-8169.patch, hbase-8169_trunk.patch,
> In the test case, we use "master.assignRegion(hri);" to assign regions to live RS or
dead RS(will be aborted during the test). While master.assignRegion may not always successfully
assign a region to the expected RS due to following error:
> 1) We firstly try to open a region in region server, let's say RS1
> 2) For some reason the region open takes more than a time out period
> 3) AM tries to reassign it and force a new plan due to the time out
> 4) the Region is re-assigned to a random RS 
> Then it cause the test case failure due to regions setup isn't in expected state.
> I attached a log with extra added logging info and some stack traces(with (new Exception()).printStackTrace()
so you can ignore java.lang.Exception). You can search region 36716be644bc9c78b3a96e0d4a43c183
to see master.assignRegion assigned a region to a randome RS. I saw the test failed once in
5 times in a loop.

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

View raw message