[HADOOP-3136] Assign multiple tasks per TaskTracker heartbeat

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.20.0
• Assignee: Arun Murthy
• Reporter: Devaraj Das
• Created: 31/Mar/08 13:06
• Updated: 08/Jul/09 16:52
• Resolved: 16/Dec/08 09:56

Description

In today's logic of finding a new task, we assign only one task per heartbeat.

We probably could give the tasktracker multiple tasks subject to the max number of free slots it has - for maps we could assign it data local tasks. We could probably run some logic to decide what to give it if we run out of data local tasks (e.g., tasks from overloaded racks, tasks that have least locality, etc.). In addition to maps, if it has reduce slots free, we could give it reduce task(s) as well. Again for reduces we could probably run some logic to give more tasks to nodes that are closer to nodes running most maps (assuming data generated is proportional to the number of maps). For e.g., if rack1 has 70% of the input splits, and we know that most maps are data/rack local, we try to schedule ~70% of the reducers there.

Thoughts?