[ https://issues.apache.org/jira/browse/HDFS-9807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993431#comment-15993431 ]
Virajith Jalaparti commented on HDFS-9807: ------------------------------------------ bq. was concerned that this will break when running tests in parallel if we have multiple test cases. I agree. It only works as long as it is used by a single test, and is used as in the current test case. bq. This is because checkstyle complained that I had added redundant {{final}} decls to a function argument. Makes sense. May be others can comment if this needs to be changed? > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org