[MAPREDUCE-4813] AM timing out during job commit

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.23.3, 2.0.1-alpha
• Fix Version/s: 2.0.3-alpha, 0.23.6
• Component/s: applicationmaster
• Target Version/s: 2.0.3-alpha, 0.23.6
• Assignee: Jason Darrell Lowe
• Reporter: Jason Darrell Lowe
• Created: 21/Nov/12 15:31
• Updated: 03/Sep/14 23:25
• Resolved: 28/Dec/12 15:10

Description

The AM calls the output committer's commitJob method synchronously during JobImpl state transitions, which means the JobImpl write lock is held the entire time the job is being committed. Holding the write lock prevents the RM allocator thread from heartbeating to the RM. Therefore if committing the job takes too long (e.g.: the job has tons of files to commit and/or the namenode is bogged down) then the AM appears to be unresponsive to the RM and the RM kills the AM attempt.

Issue Links

• relates to: MAPREDUCE-4819 AM can rerun job after reporting final job status to the client