Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 63612 invoked from network); 2 Jul 2008 22:15:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Jul 2008 22:15:08 -0000 Received: (qmail 27153 invoked by uid 500); 2 Jul 2008 22:15:07 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 27113 invoked by uid 500); 2 Jul 2008 22:15:07 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 27102 invoked by uid 99); 2 Jul 2008 22:15:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jul 2008 15:15:07 -0700 X-ASF-Spam-Status: No, hits=-1998.8 required=10.0 tests=ALL_TRUSTED,FS_REPLICA X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jul 2008 22:14:24 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 30C19234C150 for ; Wed, 2 Jul 2008 15:14:45 -0700 (PDT) Message-ID: <1747012991.1215036885198.JavaMail.jira@brutus> Date: Wed, 2 Jul 2008 15:14:45 -0700 (PDT) From: "Koji Noguchi (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Created: (HADOOP-3685) Unbalanced replication target MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Unbalanced replication target ------------------------------ Key: HADOOP-3685 URL: https://issues.apache.org/jira/browse/HADOOP-3685 Project: Hadoop Core Issue Type: Bug Components: dfs Affects Versions: 0.17.0 Reporter: Koji Noguchi Priority: Critical In HADOOP-3633, namenode was assigning some datanodes to receive hundreds of blocks in a short period which caused datanodes to go out of memroy(threads). Most of them were from remote rack. Looking at the code, {noformat} 166 chooseLocalRack(results.get(1), excludedNodes, blocksize, 167 maxNodesPerRack, results); {noformat} was sometimes not choosing the local rack of the writer(source). As a result, when a datanode goes down, other datanodes on the same rack were getting large number of blocks from remote racks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.