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

["Ewan Higgs (JIRA)" <ji...@apache.org>]

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

Ewan Higgs commented on HDFS-9807:
----------------------------------

Should the {{StorageID}} be in the write messages ({{OpWriteBlockProto}} {{OpTransferBlockProto}}, {{OpReplaceBlockProto}}, {{OpCopyBlockProto}}) as well as the {{BlockTokenIdentifier}}, or just the messages?

> Add an optional StorageID to writes
> -----------------------------------
>
>                 Key: HDFS-9807
>                 URL: https://issues.apache.org/jira/browse/HDFS-9807
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Chris Douglas
>
> 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.4#6332)

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