hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "surendra singh lilhore (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8143) HDFS Mover tool should exist after some retry when failed to move blocks.
Date Sun, 26 Apr 2015 07:40:38 GMT

    [ https://issues.apache.org/jira/browse/HDFS-8143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512929#comment-14512929
] 

surendra singh lilhore commented on HDFS-8143:
----------------------------------------------

[~szetszwo] Please can you review patch. This I got because of [HDFS-8147|https://issues.apache.org/jira/browse/HDFS-8147]

> HDFS Mover tool should exist 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)

Mime
View raw message