Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 63976 invoked from network); 3 May 2009 00:55:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 May 2009 00:55:53 -0000 Received: (qmail 74128 invoked by uid 500); 3 May 2009 00:55:52 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 74055 invoked by uid 500); 3 May 2009 00:55:52 -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 73777 invoked by uid 99); 3 May 2009 00:55:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 May 2009 00:55:51 +0000 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; Sun, 03 May 2009 00:55:50 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id BA580234C4AF for ; Sat, 2 May 2009 17:55:30 -0700 (PDT) Message-ID: <170323106.1241312130762.JavaMail.jira@brutus> Date: Sat, 2 May 2009 17:55:30 -0700 (PDT) From: "dhruba borthakur (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Issue Comment Edited: (HADOOP-3799) Design a pluggable interface to place replicas of blocks in HDFS In-Reply-To: <643300366.1216628371608.JavaMail.jira@brutus> 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/HADOOP-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705361#action_12705361 ] dhruba borthakur edited comment on HADOOP-3799 at 5/2/09 5:55 PM: ------------------------------------------------------------------ @Stefan: I completely agree with you. This patch should enable researchers to experiment with various modes of HDFS block placement without changing code-hdfs code. I plan on using this to co-locate blocks from hdfs datasets that are frequently scanner together in a small number of datanodes so that such a "join" operation gets better node/rack locality. was (Author: dhruba): @Stefan: I complete agree with you. This patch should enable researchers to experiment with various modes of HDFS block placement without changing code-hdfs code. I plan on using this to co-locate blocks from hdfs datasets that are frequently scanner together in a small number of datanodes so that such a "join" operation gets better node/rack locality. > Design a pluggable interface to place replicas of blocks in HDFS > ---------------------------------------------------------------- > > Key: HADOOP-3799 > URL: https://issues.apache.org/jira/browse/HADOOP-3799 > Project: Hadoop Core > Issue Type: Improvement > Components: dfs > Reporter: dhruba borthakur > Assignee: dhruba borthakur > Attachments: BlockPlacementPluggable.txt > > > The current HDFS code typically places one replica on local rack, the second replica on remote random rack and the third replica on a random node of that remote rack. This algorithm is baked in the NameNode's code. It would be nice to make the block placement algorithm a pluggable interface. This will allow experimentation of different placement algorithms based on workloads, availability guarantees and failure models. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.