[
https://issues.apache.org/jira/browse/HDFS-9807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated HDFS-9807:
--------------------------------
Attachment: HDFS-9807.002.patch
bq. I am planning to push the information like storageID and storageType
FsVolumeList (as described in the last suggestion in my previous comment) and
probably also into the interface for the VolumeChoosingPolicy, so it can decide
to choose the volume based on all the info.
+1 for this approach. The configured {{VolumeChoosingPolicy}} can elect to
ignore the particular storageid chosen by the NameNode, as it does now.
Uploaded a new patch with really minor changes (removing some vestigial code,
fixed findbugs, etc.). A couple questions:
* The {{BlockTokenIdentifier}} also updates the legacy, {{Writable}} token.
This wouldn't work with older clients?
* There's an assertion in {{StripedWriter}} that targetStorageIDs is not null;
does that always hold?
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
