Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A0BE99ED5 for ; Sat, 25 Feb 2012 01:32:13 +0000 (UTC) Received: (qmail 92425 invoked by uid 500); 25 Feb 2012 01:32:13 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 92374 invoked by uid 500); 25 Feb 2012 01:32:13 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 92275 invoked by uid 99); 25 Feb 2012 01:32:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 25 Feb 2012 01:32:13 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 25 Feb 2012 01:32:10 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 8B395339E29 for ; Sat, 25 Feb 2012 01:31:49 +0000 (UTC) Date: Sat, 25 Feb 2012 01:31:49 +0000 (UTC) From: "Hadoop QA (Commented) (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <1271731122.18498.1330133509571.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <652329288.51448.1329502079467.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HDFS-2966) TestNameNodeMetrics tests can fail under load MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HDFS-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13216223#comment-13216223 ] Hadoop QA commented on HDFS-2966: --------------------------------- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12516000/HDFS-2966.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/1910//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1910//console This message is automatically generated. > TestNameNodeMetrics tests can fail under load > --------------------------------------------- > > Key: HDFS-2966 > URL: https://issues.apache.org/jira/browse/HDFS-2966 > Project: Hadoop HDFS > Issue Type: Bug > Components: test > Affects Versions: 0.24.0 > Environment: OS/X running intellij IDEA, firefox, winxp in a virtualbox. > Reporter: Steve Loughran > Assignee: Steve Loughran > Priority: Minor > Fix For: 0.24.0, 0.23.2 > > Attachments: HDFS-2966.patch, HDFS-2966.patch, HDFS-2966.patch > > > I've managed to recreate HDFS-540 and HDFS-2434 by the simple technique of running the HDFS tests on a desktop with out enough memory for all the programs trying to run. Things got swapped out and the tests failed as the DN heartbeats didn't come in on time. > the tests both rely on {{waitForDeletion()}} to block the tests until the delete operation has completed, but all it does is sleep for the same number of seconds as there are datanodes. This is too brittle -it may work on a lightly-loaded system, but not on a system under heavy load where it is taking longer to replicate than expect. > Immediate fix: double, triple, the sleep time? > Better fix: have the thread block until all the DN heartbeats have finished. -- 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