You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Hairong Kuang (JIRA)" <ji...@apache.org> on 2008/10/22 22:45:44 UTC

[jira] Updated: (HADOOP-4489) Blocks have been scheduled to delete by NameNode but are not deleted on the DataNode

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

Hairong Kuang updated HADOOP-4489:
----------------------------------

    Description: 
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.

  was:
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 BB remains on the DataNode XX's disk with no timestamp change.


> 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.