hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dick King (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1073) Progress reported for pipes tasks is incorrect.
Date Thu, 22 Jul 2010 20:59:51 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891328#action_12891328
] 

Dick King commented on MAPREDUCE-1073:
--------------------------------------

In my previous comment I should have said that this patch addresses BOTH points, and is complete
modulo a forward port.

> Progress reported for pipes tasks is incorrect.
> -----------------------------------------------
>
>                 Key: MAPREDUCE-1073
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1073
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: pipes
>    Affects Versions: 0.20.1
>            Reporter: Sreekanth Ramakrishnan
>            Assignee: Dick King
>         Attachments: mapreduce-1073--2010-03-31.patch, mapreduce-1073--2010-04-06.patch,
MAPREDUCE-1073--yhadoop20--2010-07-22.patch, MAPREDUCE-1073_yhadoop20.patch
>
>
> Currently in pipes, {{org.apache.hadoop.mapred.pipes.PipesMapRunner.run(RecordReader<K1,
V1>, OutputCollector<K2, V2>, Reporter)}} we do the following:
> {code}
>         while (input.next(key, value)) {
>           downlink.mapItem(key, value);
>           if(skipping) {
>             downlink.flush();
>           }
>         }
> {code}
> This would result in consumption of all the records for current task and taking task
progress to 100% whereas the actual pipes application would be trailing behind. 

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