Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1261505921.1238458730432.JavaMail.jira@brutus>
Date: Mon, 30 Mar 2009 17:18:50 -0700 (PDT)
From: "Hairong Kuang (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-4489) Blocks have been scheduled to
 delete by NameNode but are not deleted on the DataNode
In-Reply-To: <1502658366.1224701506245.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693956#action_12693956 ] 

Hairong Kuang commented on HADOOP-4489:
---------------------------------------

This bug might be caused by HADOOP-5465. Once a datanode hits HADOOP-5465, NameNode sends an empty replication request to the data node on every reply to a heartbeat, thus not a single scheduled block deletion request can be sent to the data node.

> Blocks have been scheduled to delete by NameNode but are not deleted on the DataNode
> ------------------------------------------------------------------------------------
>
>                 Key: HADOOP-4489
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4489
>             Project: Hadoop Core
>          Issue Type: Bug
>    Affects Versions: 0.17.0
>            Reporter: Hairong Kuang
>
> NameNode sometimes scheduled a replica to be deleted as shown in the NameNode log:
> INFO org.apache.hadoop.dfs.StateChange: BLOCK* ask DataNode XX to delete blk_YY
> But block YY did not get deleted on the DataNode XX. The datanode log had no indication of where the deletion was successful or failed. The block YY remains on the DataNode XX's disk with no timestamp change.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.