[jira] Updated: (HADOOP-2275) Erroneous detection of corrupted file when namenode fails to allocate any datanodes for newly allocated block

["dhruba borthakur (JIRA)" <ji...@apache.org>]

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

dhruba borthakur updated HADOOP-2275:
-------------------------------------

    Attachment: badBlocks1.patch

If the namenode fails to allocate any datanode for a newly allocated block, it removes that block from the file before returning an exception to the client.

> Erroneous detection of corrupted file when namenode fails to allocate any datanodes for newly allocated block
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2275
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2275
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.15.0
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>         Attachments: badBlocks1.patch
>
>
> It can so happen that the namenode allocated a block for a file and then fails to allocate any datanode for this block. The namenode delivers an exception to the client. The client retries. But the block remains associated with the file (until lease expiration). This causes all client retries to fail.
> An fsck (before the lease expires) reports this block as a missing block.

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