Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 27 Apr 2015 02:38:38 +0000 (UTC)
From: "Vinayakumar B (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12820906.1429037382000.33546.1430102318439@Atlassian.JIRA>
In-Reply-To: <JIRA.12820906.1429037382000@Atlassian.JIRA>
References: <JIRA.12820906.1429037382000@Atlassian.JIRA>
 <JIRA.12820906.1429037382715@arcas>
Subject: [jira] [Updated] (HDFS-8143) HDFS Mover tool should exit after some
 retry when failed to move blocks.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinayakumar B updated HDFS-8143:
--------------------------------
    Summary: HDFS Mover tool should exit after some retry when failed to move blocks.  (was: HDFS Mover tool should exist after some retry when failed to move blocks.)

> 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: Bug
>          Components: balancer & mover
>    Affects Versions: 2.6.0
>            Reporter: surendra singh lilhore
>            Assignee: surendra singh lilhore
>            Priority: Blocker
>         Attachments: HDFS-8143.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)