hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hairong Kuang (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HADOOP-4489) Blocks have been scheduled to delete by NameNode but are not deleted on the DataNode
Date Tue, 31 Mar 2009 00:24:50 GMT

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

Hairong Kuang resolved HADOOP-4489.
-----------------------------------

    Resolution: Won't Fix

With the fixes in HADOOP-5465, HADOOP-5549, and HADOOP-5034, the problem described in this
jira should not be reproduced. Closing this jira for now. Will reopen it if we see this happen
again.

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


Mime
View raw message