hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3902) TestDatanodeBlockScanner is flaky, broke entirely after HDFS-3828
Date Wed, 12 Sep 2012 18:12:08 GMT

    [ 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

View raw message