[
https://issues.apache.org/jira/browse/HDFS-5157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13763705#comment-13763705
]
Junping Du commented on HDFS-5157:
----------------------------------
Sure. Arpit. Let's wait their feedback first. However, I think your previous
comments provide the 3rd option which I like pretty much:
bq. To keep things simple for now we can defer the decision on whether to allow
the DataNode to override the target volume or not.
I think it may be a good idea to randomly choosing a storage ID in replica
choosing for DatanodeStorageInfo, and let DataNode to override target volume
(storage ID) later in short term. Through this, we can keep replica choosing
policy simpler (without counting too much logic as VolumeChoosingPolicy) and
get rid of quick decision on depreciating VolumeChoosingPolicy. What do you all
think?
> Datanode should allow choosing the target storage
> -------------------------------------------------
>
> Key: HDFS-5157
> URL: https://issues.apache.org/jira/browse/HDFS-5157
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: datanode
> Affects Versions: Heterogeneous Storage (HDFS-2832)
> Reporter: Arpit Agarwal
> Assignee: Junping Du
> Attachments: HDFS-5157-v1.patch, HDFS-5157-v2.patch
>
>
> Datanode should allow should choosing a target Storage or target Storage Type
> as a parameter when creating a new block. Currently there are two ways in
> which the target volume is chosen (via {{VolumeChoosingPolicy#chooseVolume}}.
> # AvailableSpaceVolumeChoosingPolicy
> # RoundRobinVolumeChoosingPolicy
> BlockReceiver and receiveBlock should also accept a new parameter for target
> storage or storage type.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
