[
https://issues.apache.org/jira/browse/HDFS-11293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811415#comment-15811415
]
Rakesh R commented on HDFS-11293:
---------------------------------
Good catch [~yuanbo]. Thanks for the patch, [~umamaheswararao].
Fix looks good to me. Just few comments on tests:
# Can we add try-finally and add {{shutdownCluster();}} in the finally block of
{{testBlockMoveInSameAndRemoteDatanodesWithWARM}}
# Please fix typo {{ssatisfyStoragePolicy}}. Also, I hope in the example, it
should be DN1 and DN2, please correct the same.
{code}
+ * ssatisfyStoragePolicy, then block should move to DN1[ARCHIVE] and
+ * DN1[ARCHIVE] successfully.
{code}
> [SPS]: Local DN should be given preference 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
> Components: namenode
> Affects Versions: HDFS-10285
> 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: [email protected]
For additional commands, e-mail: [email protected]
