Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 59796 invoked from network); 3 Feb 2007 00:33:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Feb 2007 00:33:30 -0000 Received: (qmail 37781 invoked by uid 500); 3 Feb 2007 00:33:34 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 37751 invoked by uid 500); 3 Feb 2007 00:33:34 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 37706 invoked by uid 99); 3 Feb 2007 00:33:33 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Feb 2007 16:33:33 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Feb 2007 16:33:26 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 3E73E714057 for ; Fri, 2 Feb 2007 16:33:06 -0800 (PST) Message-ID: <11296609.1170462786253.JavaMail.jira@brutus> Date: Fri, 2 Feb 2007 16:33:06 -0800 (PST) From: "Hairong Kuang (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Updated: (HADOOP-692) Rack-aware Replica Placement In-Reply-To: <5324842.1163011853487.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hairong Kuang updated HADOOP-692: --------------------------------- Fix Version/s: 0.11.0 Affects Version/s: (was: 0.8.0) 0.10.1 Status: Patch Available (was: Open) > Rack-aware Replica Placement > ---------------------------- > > Key: HADOOP-692 > URL: https://issues.apache.org/jira/browse/HADOOP-692 > Project: Hadoop > Issue Type: Improvement > Components: dfs > Affects Versions: 0.10.1 > Reporter: Hairong Kuang > Assigned To: Hairong Kuang > Fix For: 0.11.0 > > Attachments: rack.patch, Rack_aware_HDFS_proposal.pdf > > > This issue assumes that HDFS runs on a cluster of computers that spread across many racks. Communication between two nodes on different racks needs to go through switches. Bandwidth in/out of a rack may be less than the total bandwidth of machines in the rack. The purpose of rack-aware replica placement is to improve data reliability, availability, and network bandwidth utilization. The basic idea is that each data node determines to which rack it belongs at the startup time and notifies the name node of the rack id upon registration. The name node maintains a rackid-to-datanode map and tries to place replicas across racks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.