[
https://issues.apache.org/jira/browse/HADOOP-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546323
]
Hadoop QA commented on HADOOP-2275:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12370226/badBlocks1.patch
against trunk revision r598984.
@author +1. The patch does not contain any @author tags.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new compiler warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests -1. The patch failed core unit tests.
contrib tests -1. The patch failed contrib unit tests.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1189/testReport/
Findbugs warnings:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1189/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1189/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1189/console
This message is automatically generated.
> 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, 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.