hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-2275) Erroneous detection of corrupted file when namenode fails to allocate any datanodes for newly allocated block
Date Thu, 29 Nov 2007 13:54:43 GMT

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

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

       Resolution: Fixed
    Fix Version/s: 0.16.0
           Status: Resolved  (was: Patch Available)

I just committed this.

> 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
>             Fix For: 0.16.0
>
>         Attachments: badBlocks1.patch, 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.


Mime
View raw message