Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 13 Sep 2012 05:12:08 +1100 (NCT)
From: "Eli Collins (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <1233428522.70740.1347473529049.JavaMail.jiratomcat@arcas>
In-Reply-To: <509878970.51019.1347036007525.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HDFS-3902) TestDatanodeBlockScanner is flaky,
 broke entirely after HDFS-3828
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eli Collins commented on HDFS-3902:
-----------------------------------

Nice debugging Andy.  +1 to this patch, let's pull the 2nd failure scenario you describe out to another jira and address there.

The test failures are unrelated, I filed HDFS-3930 for TestBPOfferService. TestWebHDFS and TestPersistBlocks both failed due to networking issue (connection refused to a grid machine).
                
> TestDatanodeBlockScanner is flaky, broke entirely after HDFS-3828
> -----------------------------------------------------------------
>
>                 Key: HDFS-3902
>                 URL: https://issues.apache.org/jira/browse/HDFS-3902
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.0.0-alpha
>            Reporter: Andy Isaacson
>            Assignee: Andy Isaacson
>            Priority: Minor
>         Attachments: hdfs3902.txt
>
>
> Since HDFS-3828 fixed the block scanner to not repeatedly rescan small blockpools, TestDatanodeBlockScanner times out after 13 minutes in {{waitReplication}}.

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