hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2314) TestBlockReplacement occasionally get into an infinite loop
Date Sat, 01 Dec 2007 06:46:43 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547383
] 

Hadoop QA commented on HADOOP-2314:
-----------------------------------

+1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12370690/block.patch
against trunk revision r600019.

    @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/1226/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1226/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1226/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1226/console

This message is automatically generated.

> TestBlockReplacement occasionally get into an infinite loop
> -----------------------------------------------------------
>
>                 Key: HADOOP-2314
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2314
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.15.1
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>             Fix For: 0.16.0
>
>         Attachments: block.patch
>
>
> It turns out that in the case that tests an invalid deletion hint, either the newNode
or source may be choosen to be deleted as an exessive replica since both of the nodes are
on the same rack. The test assumes that only newNode will be deleted and wait for its deletion.
This causes an infinite loop when source is chosen to be deleted.

-- 
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