[ https://issues.apache.org/jira/browse/MAPREDUCE-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539698#comment-13539698 ]
Robert Joseph Evans commented on MAPREDUCE-4813: ------------------------------------------------ A quick look at the patch looks OK to me. I need to dig into it in more detail. Also the patch no longer compiles on trunk. Could you please upmerge. The generated state transition charts make looking at the events a lot simpler, but that does not work if the code does not compile. > AM timing out during job commit > ------------------------------- > > Key: MAPREDUCE-4813 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4813 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: applicationmaster > Affects Versions: 0.23.3, 2.0.1-alpha > Reporter: Jason Lowe > Assignee: Jason Lowe > Priority: Critical > Attachments: JobImplStateMachine.pdf, MAPREDUCE-4813-2.patch, > MAPREDUCE-4813-2.patch, MAPREDUCE-4813.patch, MAPREDUCE-4813.patch, > MAPREDUCE-4813.patch > > > 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira