Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 16 Jun 2015 19:29:00 +0000 (UTC)
From: "surendra singh lilhore (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12835568.1433459887000.87472.1434482940857@Atlassian.JIRA>
In-Reply-To: <JIRA.12835568.1433459887000@Atlassian.JIRA>
References: <JIRA.12835568.1433459887000@Atlassian.JIRA>
 <JIRA.12835568.1433459887191@arcas>
Subject: [jira] [Updated] (HDFS-8541) Mover should exit with
 NO_MOVE_PROGRESS if there is no move progress
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-8541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

surendra singh lilhore updated HDFS-8541:
-----------------------------------------
    Attachment: HDFS-8541.patch

Attached initial patch, please review.

I think no need of test case, TestMover.testMoverFailedRetry() is enough. 

> 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: Sub-task
>          Components: balancer & mover
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: surendra singh lilhore
>            Priority: Minor
>         Attachments: HDFS-8541.patch
>
>
> 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)