Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 25 Apr 2014 11:24:15 +0000 (UTC)
From: "Vinayakumar B (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12708559.1397581540595.180233.1398425055876@arcas>
In-Reply-To: <JIRA.12708559.1397581540595@arcas>
References: <JIRA.12708559.1397581540595@arcas>
Subject: [jira] [Commented] (HDFS-6247) Avoid timeouts for replaceBlock()
 call by sending intermediate responses to Balancer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinayakumar B commented on HDFS-6247:
-------------------------------------

test failure is not related to current patch.

> Avoid timeouts for replaceBlock() call by sending intermediate responses to Balancer
> ------------------------------------------------------------------------------------
>
>                 Key: HDFS-6247
>                 URL: https://issues.apache.org/jira/browse/HDFS-6247
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: balancer, datanode
>    Affects Versions: 2.4.0
>            Reporter: Vinayakumar B
>            Assignee: Vinayakumar B
>         Attachments: HDFS-6247.patch, HDFS-6247.patch
>
>
> Currently there is no response sent from target Datanode to Balancer for the replaceBlock() calls.
> Since the Block movement for balancing is throttled, complete block movement will take time and this could result in timeout at Balancer, which will be trying to read the status message.
>  
> To Avoid this during replaceBlock() call in in progress Datanode  can send IN_PROGRESS status messages to Balancer to avoid timeouts and treat BlockMovement as  failed.


--
This message was sent by Atlassian JIRA
(v6.2#6252)