[MAPREDUCE-3972] Locking and exception issues in JobHistory Server.

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.23.2
• Fix Version/s: 0.23.3, 2.0.2-alpha
• Component/s: mrv2
• Target Version/s: 0.23.3
• Hadoop Flags: Reviewed
• Assignee: Robert Joseph Evans
• Reporter: Robert Joseph Evans
• Created: 05/Mar/12 19:22
• Updated: 11/Oct/12 17:48
• Resolved: 18/Apr/12 02:01

Description

The JobHistory server's locking is inconsistent and wrong in some cases. This is not super critical because the issues would only show up if a job is being cleaned up or moved from intermediate done to done, at the same time it is being parsed into a CompletedJob. However the locking is slowing down the server in some cases, and is a ticking time bomb that needs to be addressed.

As part of this too we need to be sure that the Cleaner and Intermediate to Done migration threads handle exceptions properly. Now it appears that the exception is logged, and the thread just shuts down. This means that the history server could still be up and running for weeks and never remove old jobs.

Issue Links

• is duplicated by: MAPREDUCE-4080 FileNotFoundException while accessing job configuration from UI.
• is related to: MAPREDUCE-4055 Job history files are not getting copied from "intermediate done" directory to "done" directory