Issue Details (XML | Word | Printable)

Key: MAPREDUCE-262
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Amar Kamat
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Hadoop Map/Reduce

Optimize finding of speculative tasks

Created: 22/Feb/08 11:16 AM   Updated: 20/Jun/09 07:51 AM
Return to search
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Blocker
 


 Description  « Hide
Assuming HADOOP-2119 provides better data structures for handling running TIPs, finding new speculative tasks can be further optimized. Two of which could be
1) conf.getMapSpeculativeExecution() and conf.getReduceSpeculativeExecution() should be moved to JobInProgress. A simple check for this boolean can prove useful before checking for speculative tasks. This will be useful for jobs with large maps and reducers where scanning all the TIPs can be costly.
2) Since the progress of a TIP changes only when TaskInProgress.recomputeProgress() is invoked, it makes more sense to check for speculation in JobInProgress.updateTaskStatus() and move the TIPs that can be speculated to the front of the running queue.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Amar Kamat made changes - 22/Feb/08 11:17 AM
Field Original Value New Value
Link This issue is blocked by HADOOP-2119 [ HADOOP-2119 ]
Owen O'Malley made changes - 20/Jun/09 07:51 AM
Component/s mapred [ 12310690 ]
Key HADOOP-2874 MAPREDUCE-262
Project Hadoop Common [ 12310240 ] Hadoop Map/Reduce [ 12310941 ]