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 BE8079E68 for ; Thu, 12 Apr 2012 18:27:42 +0000 (UTC) Received: (qmail 49012 invoked by uid 500); 12 Apr 2012 18:27:42 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 48980 invoked by uid 500); 12 Apr 2012 18:27:42 -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 48972 invoked by uid 99); 12 Apr 2012 18:27:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Apr 2012 18:27:42 +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; Thu, 12 Apr 2012 18:27:40 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 34B34367EC9 for ; Thu, 12 Apr 2012 18:27:19 +0000 (UTC) Date: Thu, 12 Apr 2012 18:27:19 +0000 (UTC) From: "Hadoop QA (Commented) (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <1326622048.18484.1334255239236.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1570488827.14708.1334179998537.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HDFS-3256) HDFS considers blocks under-replicated if topology script is configured with only 1 rack MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252695#comment-13252695 ] Hadoop QA commented on HDFS-3256: --------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12522445/HDFS-3256.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 2 new or modified test files. +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 failed these unit tests: org.apache.hadoop.hdfs.server.blockmanagement.TestBlocksWithNotEnoughRacks +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/2261//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2261//console This message is automatically generated. > HDFS considers blocks under-replicated if topology script is configured with only 1 rack > ---------------------------------------------------------------------------------------- > > Key: HDFS-3256 > URL: https://issues.apache.org/jira/browse/HDFS-3256 > Project: Hadoop HDFS > Issue Type: Bug > Affects Versions: 2.0.0 > Reporter: Aaron T. Myers > Assignee: Aaron T. Myers > Attachments: HDFS-3256.patch, HDFS-3256.patch, HDFS-3256.patch, HDFS-3256.patch, HDFS-3256.patch, HDFS-3256.patch > > > HDFS treats the mere presence of a topology script being configured as evidence that there are multiple racks. If there is in fact only a single rack, the NN will try to place the blocks on at least two racks, and thus blocks will be considered to be under-replicated. -- 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