Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 11 Oct 2012 17:47:36 +0000 (UTC)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <112051057.29343.1349977656851.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <1022642189.9117.1330639438363.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (HDFS-3037)
 TestMulitipleNNDataBlockScanner#testBlockScannerAfterRestart is racy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Arun C Murthy closed HDFS-3037.
-------------------------------

    
> 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.23.3, 2.0.2-alpha
>
>         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
For more information on JIRA, see: http://www.atlassian.com/software/jira