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

Posted to hdfs-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/17 21:55:05 UTC

[jira] [Commented] (HDFS-139) Datanode block deletions can get starved.

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

Allen Wittenauer commented on HDFS-139:
---------------------------------------

I suspect we can close this as fixed, but someone should verify.

> Datanode block deletions can get starved.
> -----------------------------------------
>
>                 Key: HDFS-139
>                 URL: https://issues.apache.org/jira/browse/HDFS-139
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Raghu Angadi
>
> See the relevant [comment|https://issues.apache.org/jira/browse/HADOOP-2576?focusedCommentId=12561866#action_12561866] in HADOOP-2576.
> Namenode asks a datanode to delete blocks only if datanode is not asked to transfer a block. Namenode should send both the blocks to transfer and to delete. The problem gets worse if configured heartbeat is longer.



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