[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=15878093#comment-15878093 ] 

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

To answer the previous question: I'm adding the storage ID to all the messages that also send a targetStorageType (i.e. {{OpWriteBlockProto}},{{OpTransferBlockProto}}, {{OpReplaceBlockProto}}, and not {{OpCopyBlockProto}}).

The storageID should also go into the {{BlockTokenIdentifier}}. With HDFS-11026 merged, I think it's best to only put this into the protobuf version. But I am open to listening to arguments for putting it in the Legacy token.

> 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
>            Assignee: Ewan Higgs
>
> 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