hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-3422) TestStandbyIsHot timeouts too aggressive
Date Thu, 17 May 2012 00:20:06 GMT

     [ https://issues.apache.org/jira/browse/HDFS-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Todd Lipcon updated HDFS-3422:

    Attachment: hdfs-3422.txt

Following patch more explicitly forces replication work to be calculated in an expedient matter,
increases timeouts, etc. I looped this for an hour or so locally and it passed every time.
> 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