hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-4990) Block placement for storage types
Date Mon, 16 Sep 2013 23:30:52 GMT

     [ https://issues.apache.org/jira/browse/HDFS-4990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Tsz Wo (Nicholas), SZE updated HDFS-4990:

    Attachment: h4990_20130917.patch

h4990_20130917.patch: reverts the changes TestWebHdfsDataLocality which I forgot to do it
in the previous patch.
> Block placement for storage types
> ---------------------------------
>                 Key: HDFS-4990
>                 URL: https://issues.apache.org/jira/browse/HDFS-4990
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>            Reporter: Suresh Srinivas
>            Assignee: Tsz Wo (Nicholas), SZE
>         Attachments: h4990_20130909.patch, h4990_20130916.patch, h4990_20130917.patch
> Currently block location for writes are made based on:
> # Datanode load (number of transceivers)
> # Space left on datanode
> # Topology
> With storage abstraction, namenode must choose a storage instead of a datanode for block
placement. It also needs to consider storage type, load on the storage etc.
> As an additional benefit, currently HDFS support heterogeneous nodes (nodes with different
number of spindles etc.) poorly. This work should help solve that issue as well.

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

View raw message