hadoop-hdfs-issues mailing list archives

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

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

Hudson commented on HDFS-3037:
------------------------------

Integrated in Hadoop-Common-trunk-Commit #1819 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1819/])
    HDFS-3037. TestMulitipleNNDataBlockScanner#testBlockScannerAfterRestart is racy. Contributed
by Aaron T. Myers. (Revision 1296016)

     Result = SUCCESS
atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1296016
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/TestMulitipleNNDataBlockScanner.java

                
> 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
>             Fix For: 0.24.0
>
>         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

        

Mime
View raw message