[
https://issues.apache.org/jira/browse/HADOOP-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528670
]
Hadoop QA commented on HADOOP-1904:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12365906/RedundantAddBlock.patch
against trunk revision r577010.
@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 passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/787/testReport/
Findbugs warnings:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/787/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/787/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/787/console
This message is automatically generated.
> ArrayIndexOutOfBoundException in BlocksMap
> ------------------------------------------
>
> Key: HADOOP-1904
> URL: https://issues.apache.org/jira/browse/HADOOP-1904
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.15.0
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Priority: Blocker
> Fix For: 0.15.0
>
> Attachments: RedundantAddBlock.patch
>
>
> If the name-node receives a duplicate report of a written block from a
> data-node it does not insert
> the block into the block map but mistakenly inserts it into the list of
> blocks belonging to the data-node,
> placing it into the beginning of the list. Since the block is not removed
> from the list prior to the insertion,
> the list itself becomes corrupted.
> This patch fixes the problem. I also reorganized the add/removeNode and
> add/removeBlock methods
> in order to avoid similar bugs in the future.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
