You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Virajith Jalaparti (JIRA)" <ji...@apache.org> on 2017/05/01 17:48:04 UTC

[jira] [Updated] (HDFS-9807) Add an optional StorageID to writes

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

Virajith Jalaparti updated HDFS-9807:
-------------------------------------
    Attachment: HDFS-9807.009.patch

Posting a modified patch fixing some of the checkstyle errors.

> Add an optional StorageID to writes
> -----------------------------------
>
>                 Key: HDFS-9807
>                 URL: https://issues.apache.org/jira/browse/HDFS-9807
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 3.0.0-alpha2
>            Reporter: Chris Douglas
>            Assignee: Ewan Higgs
>         Attachments: HDFS-9807.001.patch, HDFS-9807.002.patch, HDFS-9807.003.patch, HDFS-9807.004.patch, HDFS-9807.005.patch, HDFS-9807.006.patch, HDFS-9807.007.patch, HDFS-9807.008.patch, HDFS-9807.009.patch
>
>
> The {{BlockPlacementPolicy}} considers specific storages, but when the replica is written the DN {{VolumeChoosingPolicy}} is unaware of any preference or constraints from other policies affecting placement. This limits heterogeneity to the declared storage types, which are treated as fungible within the target DN. It should be possible to influence or constrain the DN policy to select a particular storage.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org