Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 25 May 2012 07:17:23 +0000 (UTC)
From: "Konstantin Shvachko (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <1582061341.786.1337930243461.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <2099430399.633.1337928264085.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HDFS-3463) DFSTestUtil.waitCorruptReplicas()
 should not use file reading time as a timeout measure.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Konstantin Shvachko commented on HDFS-3463:
-------------------------------------------

TestDatanodeBlockScanner.testBlockCorruptionRecoveryPolicy1 failed because DFSTestUtil.waitCorruptReplicas() reads some file 50 times and checks if the corruption is detected after each read. In the run that time was enough for the DN to restart, but not enough for NN to detect the corruption.
I see fifty "Waiting for 1 corrupt replicas", which means all 50 reads have been done, but don't see "NameSystem.addToCorruptReplicasMap:" in the log indicating that corruption was not detected.
                
> DFSTestUtil.waitCorruptReplicas() should not use file reading time as a timeout measure.
> ----------------------------------------------------------------------------------------
>
>                 Key: HDFS-3463
>                 URL: https://issues.apache.org/jira/browse/HDFS-3463
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 3.0.0
>            Reporter: Konstantin Shvachko
>         Attachments: testBlockCorruptionRecoveryPolicy1.log.htm
>
>
> Tests fail because DFSTestUtil.waitCorruptReplicas() does not wait long enough.

--
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