[MAPREDUCE-3944] JobHistory web services are slower then the UI and can easly overload the JH

• Type: Sub-task
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.23.1, 0.23.2
• Fix Version/s: 0.23.2
• Component/s: mrv2
• Target Version/s: 0.23.2
• Hadoop Flags: Reviewed
• Assignee: Robert Joseph Evans
• Reporter: Robert Joseph Evans
• Created: 29/Feb/12 22:44
• Updated: 02/May/13 02:29
• Resolved: 06/Mar/12 19:53

Description

When our first customer started using the Job History web services today the History Server ground to a halt. We found 250 Jetty threads stuck on the following stack trace.

   java.lang.Thread.State: BLOCKED (on object monitor)
        at org.apache.hadoop.mapreduce.v2.hs.JobHistory.getJob(JobHistory.java:898)
        - waiting to lock <0x00002aaab364ba60> (a org.apache.hadoop.mapreduce.v2.hs.JobHistory)
        at org.apache.hadoop.mapreduce.v2.hs.webapp.HsWebServices.getJobs(HsWebServices.java:188)

HsWebServices.java:188 corresponds to the /mapreduce/jobs service.

Looking at the code there are a number of optimizations that need to be done to improve its performance.

Issue Links

• depends upon: MAPREDUCE-3954 Clean up passing HEAPSIZE to yarn and mapred commands.