hadoop-hdfs-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] (HDFS-3422) TestStandbyIsHot timeouts too aggressive
Date Thu, 17 May 2012 01:54:08 GMT

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

Hadoop QA commented on HDFS-3422:

+1 overall.  Here are the results of testing the latest attachment 
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 1 new or modified test files.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 eclipse:eclipse.  The patch built with eclipse:eclipse.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit

    +1 core tests.  The patch passed unit tests in hadoop-hdfs-project/hadoop-hdfs.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/2450//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2450//console

This message is automatically generated.
> TestStandbyIsHot timeouts too aggressive
> ----------------------------------------
>                 Key: HDFS-3422
>                 URL: https://issues.apache.org/jira/browse/HDFS-3422
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 2.0.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>         Attachments: hdfs-3422.txt
> I've seen TestStandbyIsHot timeout a few times waiting for replication to change, but
when I look at the logs, it appears everything is fine. The block deletions are just a bit
slow in being processed.
> To improve the test we should either increase the timeouts, or explicitly trigger heartbeats
and replication work after changing the desired replication levels.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message