[
https://issues.apache.org/jira/browse/HDFS-11293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G updated HDFS-11293:
---------------------------------------
Attachment: HDFS-11293-HDFS-10285-01.patch
Thank you [~yuanbo] for reviewing the patch.
Its a good catch. Yes we can remove source element as we already selected it.
Attached a patch by incorporating your testcase and also took advantage to
remove unused parameter 'existing' from the code and added expected targets
meeting check instead of depending on source list iterations for more
correctness.
Please review the patch!
> [SPS]: Local DN should be given prefernce as source node, when target
> available in same node
> --------------------------------------------------------------------------------------------
>
> Key: HDFS-11293
> URL: https://issues.apache.org/jira/browse/HDFS-11293
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Yuanbo Liu
> Assignee: Uma Maheswara Rao G
> Priority: Critical
> Attachments: HDFS-11293-HDFS-10285-00.patch,
> HDFS-11293-HDFS-10285-01.patch
>
>
> In {{FsDatasetImpl#createTemporary}}, we use {{volumeMap}} to get replica
> info by block pool id. But in this situation:
> {code}
> datanode A => {DISK, SSD}, datanode B => {DISK, ARCHIVE}.
> 1. the same block replica exists in A[DISK] and B[DISK].
> 2. the block pool id of datanode A and datanode B are the same.
> {code}
> Then we start to change the file's storage policy and move the block replica
> in the cluster. Very likely we have to move block from B[DISK] to A[SSD], at
> this time, datanode A throws ReplicaAlreadyExistsException.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
