You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "surendra singh lilhore (JIRA)" <ji...@apache.org> on 2015/06/05 02:37:38 UTC
[jira] [Commented] (HDFS-8541) Mover should exit with
NO_MOVE_PROGRESS if there is no move progress
[ https://issues.apache.org/jira/browse/HDFS-8541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573877#comment-14573877 ]
surendra singh lilhore commented on HDFS-8541:
----------------------------------------------
Thanks [~szetszwo] for reporting this Improvement, I will update the path soon...
> Mover should exit with NO_MOVE_PROGRESS if there is no move progress
> --------------------------------------------------------------------
>
> Key: HDFS-8541
> URL: https://issues.apache.org/jira/browse/HDFS-8541
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: balancer & mover
> Reporter: Tsz Wo Nicholas Sze
> Assignee: surendra singh lilhore
> Priority: Minor
>
> HDFS-8143 changed Mover to exit after some retry when failed to move blocks. Two additional suggestions:
> # Mover retry counter should be incremented only if all moves fail. If there are some successful moves, the counter should be reset.
> # Mover should exit with NO_MOVE_PROGRESS instead of IO_EXCEPTION in case of failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)