Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <33036296.32761272635458459.JavaMail.jira@thor>
Date: Fri, 30 Apr 2010 09:50:58 -0400 (EDT)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-1120) Make DataNode's block-to-device
 placement policy pluggable
In-Reply-To: <31923739.2271272534954514.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862675#action_12862675 ] 

dhruba borthakur commented on HDFS-1120:
----------------------------------------

do you have a use-case in mind when such a policy if beneficial and why the current policy is inadequate?

is a policy  that tries to keep all disks at the same usage capacity better then the round-robin one? especially when disks can die, get repaired and then put back into the same system?

> Make DataNode's block-to-device placement policy pluggable
> ----------------------------------------------------------
>
>                 Key: HDFS-1120
>                 URL: https://issues.apache.org/jira/browse/HDFS-1120
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: data-node
>            Reporter: Jeff Hammerbacher
>
> As discussed on the mailing list, as the number of disk drives per server increases, it would be useful to allow the DataNode's policy for new block placement to grow in sophistication from the current round-robin strategy.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.