[
https://issues.apache.org/jira/browse/HDFS-8143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625491#comment-14625491
]
Hudson commented on HDFS-8143:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #8158 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/8158/])
Add HDFS-8143 to CHANGES.txt. (szetszwo: rev
f7c8311e9836ad1a1a2ef6eca8b42fd61a688164)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
> HDFS Mover tool should exit after some retry when failed to move blocks.
> ------------------------------------------------------------------------
>
> Key: HDFS-8143
> URL: https://issues.apache.org/jira/browse/HDFS-8143
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: balancer & mover
> Affects Versions: 2.6.0
> Reporter: Surendra Singh Lilhore
> Assignee: Surendra Singh Lilhore
> Priority: Minor
> Fix For: 2.7.1
>
> Attachments: HDFS-8143.patch, HDFS-8143_1.patch, HDFS-8143_2.patch,
> HDFS-8143_3.patch
>
>
> Mover is not coming out in case of failed to move blocks.
> {code}
> hasRemaining |= Dispatcher.waitForMoveCompletion(storages.targets.values());
> {code}
> {{Dispatcher.waitForMoveCompletion()}} will always return true if some blocks
> migration failed. So hasRemaining never become false.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
