[HADOOP-1719] Improve the utilization of shuffle copier threads

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.16.0
• Labels: pull-request-available
• Assignee: Amar Kamat
• Reporter: Devaraj Das
• Created: 16/Aug/07 05:51
• Updated: 06/Sep/20 06:42
• Resolved: 03/Jan/08 12:16

Description

In the current design, the scheduling of copies is done and the scheduler (the main loop in fetchOutputs) won't schedule anything until it hears back from at least one of the copier threads. Due to this, the main loop won't query the TaskTracker asking for new map locations and may not be using all the copiers effectively. This may not be an issue for small-sized map outputs, where at steady state, the frequency of such notifications is frequent.
Ideally, we should schedule all what we can, and, depending on how busy we currently are, query the tasktracker for more map locations.

Issue Links

• links to: GitHub Pull Request #2278