[MAPREDUCE-1533] Reduce or remove usage of String.format() usage in CapacityTaskScheduler.updateQSIObjects and Counters.makeEscapedString()

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.20.1
• Fix Version/s: 0.22.0
• Component/s: jobtracker
• Hadoop Flags: Reviewed
• Release Note: Incremental enhancements to the JobTracker to optimize heartbeat handling.
• Assignee: Dick King
• Reporter: Rajesh Balamohan
• Created: 25/Feb/10 05:06
• Updated: 12/Dec/11 06:19
• Resolved: 06/Jun/10 06:13

Description

When short jobs are executed in hadoop with OutOfBandHeardBeat=true, JT executes heartBeat() method heavily. This internally makes a call to CapacityTaskScheduler.updateQSIObjects().

CapacityTaskScheduler.updateQSIObjects(), internally calls String.format() for setting the job scheduling information. Based on the datastructure size of "jobQueuesManager" and "queueInfoMap", the number of times String.format() gets executed becomes very high. String.format() internally does pattern matching which turns to be out very heavy (This was revealed while profiling JT. Almost 57% of time was spent in CapacityScheduler.assignTasks(), out of which String.format() took 46%.

Would it be possible to do String.format() only at the time of invoking JobInProgress.getSchedulingInfo?. This might reduce the pressure on JT while processing heartbeats.

Issue Links

• incorporates: MAPREDUCE-1685 Debug statements affecting performance of JobTracker.heartbeat