hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3037) TestMulitipleNNDataBlockScanner#testBlockScannerAfterRestart is racy
Date Fri, 02 Mar 2012 01:26:59 GMT

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

Aaron T. Myers commented on HDFS-3037:

Pretty sure the TestHFlush failure is spurious and unrelated to this patch. I suspect it's
due to HDFS-3041. I just ran TestHFlush locally several times with the patch applied and it
passed just fine.

I'm going to commit this momentarily.
> TestMulitipleNNDataBlockScanner#testBlockScannerAfterRestart is racy
> --------------------------------------------------------------------
>                 Key: HDFS-3037
>                 URL: https://issues.apache.org/jira/browse/HDFS-3037
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.24.0
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>            Priority: Minor
>         Attachments: HDFS-3037.patch
> In this test, we restart a DN in a running cluster, call MiniDFS#waitActive, and then
assert some things about the DN. Trouble is, MiniDFSCluster#waitActive won't wait any time
at all, since the DN had previously registered with the NN and the NN never had time to realize
the DN was dead.

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