-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 0.23.0
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Tags:localjobrunner reduce progress
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.
- is part of
-
MAPREDUCE-2106 Emulate CPU Usage of Tasks in GridMix3
-
- Closed
-
-
MAPREDUCE-2492 [MAPREDUCE] The new MapReduce API should make available task's progress to the task
-
- Closed
-