[MAPREDUCE-2519] Progress reported by a reduce task executed via LocalJobRunner is incorrect

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 0.23.0
• Labels: localjobrunner progress reduce
• Tags: localjobrunner reduce progress
• Assignee: Amar Kamat
• Reporter: Amar Kamat
• Created: 19/May/11 08:26
• Updated: 23/May/11 17:15
• Resolved: 23/May/11 17:15

Description

ReduceTask splits its progress reporting into 3 phases
1. Copy
2. Shuffule
3. Reduce

When the reduce task is run using a LocalJobRunner, the copy phase is ignored (skipped) but the progress is not updated. This results in a mismatch in the Reduce task's progress.

Issue Links

• is part of: MAPREDUCE-2106 Emulate CPU Usage of Tasks in GridMix3
• is part of: MAPREDUCE-2492 [MAPREDUCE] The new MapReduce API should make available task's progress to the task