[
https://issues.apache.org/jira/browse/HDFS-9807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewan Higgs updated HDFS-9807:
-----------------------------
Attachment: HDFS-9807.007.patch
Adding a patch that fixes check-style issues and adds a nose-tail test using
{{MiniDFSCluster}}.
Note: the test just checks that {storageId}} passed into the
{{VolumeChoosingPolicy}} is part of the volume list. It doesn't test that it's
the same as the one sent by the NN as part of the request. I wasn't sure of the
best way to get the value from the {{BlockPlacementPolicy}} into the
{{VolumeChoosingPolicy}} for comparison. If you think it's required and have a
good idea of how to connect them then let me know what you think.
> 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
>
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
