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 540A4D95C for ; Mon, 17 Sep 2012 18:29:08 +0000 (UTC) Received: (qmail 47121 invoked by uid 500); 17 Sep 2012 18:29:08 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 47030 invoked by uid 500); 17 Sep 2012 18:29:08 -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 46959 invoked by uid 99); 17 Sep 2012 18:29:08 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Sep 2012 18:29:08 +0000 Date: Tue, 18 Sep 2012 05:29:07 +1100 (NCT) From: "Sumadhur Reddy Bolli (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <1312882767.88827.1347906548025.JavaMail.jiratomcat@arcas> In-Reply-To: <537078260.54178.1340668183942.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Updated] (HDFS-3564) Design enhancements to the pluggable blockplacementpolicy 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-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumadhur Reddy Bolli updated HDFS-3564: --------------------------------------- Description: Currently, it is assumed that no placement policy other than the default can work with the balancer and that the minimum racks required for any placement policy is always 2. The attached pdf suggests enhancements to the existing block placement policy abstraction to enable the following a) Let placement policies decide if they are compatible with balancer b) Provide an api to move blocks for balancing c) Let the placement policy decide the minimum number of racks given the replication factor was: Currently, it is assumed that no placement policy other than the default can work with the balancer and that the minimum racks required for any placement policy is always 2. The attached pdf suggests enhancements to the existing block placement policy abstraction to enable the following a) Let placement policies decide if they are compatible with balancer b) Provide an api to move blocks that can be used by the balancer for balancing c) Let the placment policy decide the minimum no of racks give > Design enhancements to the pluggable blockplacementpolicy > --------------------------------------------------------- > > Key: HDFS-3564 > URL: https://issues.apache.org/jira/browse/HDFS-3564 > Project: Hadoop HDFS > Issue Type: Improvement > Components: name-node > Reporter: Sumadhur Reddy Bolli > Assignee: Sumadhur Reddy Bolli > Fix For: 1-win > > Attachments: blockPlacementPolicy enhancements.pdf, policyenhancements-branch-1-win.patch > > > Currently, it is assumed that no placement policy other than the default can work with the balancer and that the minimum racks required for any placement policy is always 2. The attached pdf suggests enhancements to the existing block placement policy abstraction to enable the following > a) Let placement policies decide if they are compatible with balancer > b) Provide an api to move blocks for balancing > c) Let the placement policy decide the minimum number of racks given the replication factor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira