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-2048) DISTCP mapper should report progress more often
Date Sat, 13 Oct 2007 10:29:50 GMT

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

Hadoop QA commented on HADOOP-2048:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12367674/2048.patch
against trunk revision r584336.

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

This message is automatically generated.

> DISTCP mapper should report progress more often
> -----------------------------------------------
>
>                 Key: HADOOP-2048
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2048
>             Project: Hadoop
>          Issue Type: Bug
>            Reporter: Runping Qi
>            Assignee: Chris Douglas
>         Attachments: 2048.patch
>
>
> When I ran DISTCP to copy files from one dfs to another, I noticed that some mappers
got killed due to failing to report status for 606 seconds. 
> I noticed that the mappers try to make a progress report for every 32MB copied. A better
way to ensure progress is to use a time interval since last report.

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