[ https://issues.apache.org/jira/browse/MAPREDUCE-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Joseph Evans updated MAPREDUCE-4797: ------------------------------------------- Resolution: Fixed Fix Version/s: 0.23.5 2.0.3-alpha 3.0.0 Status: Resolved (was: Patch Available) Thanks Jason, I put this into trunk, branch-2, and branch-0.23 > LocalContainerAllocator can loop forever trying to contact the RM > ----------------------------------------------------------------- > > Key: MAPREDUCE-4797 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4797 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: applicationmaster > Affects Versions: 0.23.3, 2.0.1-alpha > Reporter: Jason Lowe > Assignee: Jason Lowe > Fix For: 3.0.0, 2.0.3-alpha, 0.23.5 > > Attachments: MAPREDUCE-4797.patch, MAPREDUCE-4797.patch > > > If LocalContainerAllocator has trouble communicating with the RM it can end > up retrying forever if the nature of the error is not a YarnException. > This can be particulary bad if the connection went down because the cluster > was reset such that the RM and NM have lost track of the process and > therefore nothing else will eventually kill the process. In this scenario, > the looping AM continues to pelt the RM with connection requests every second > using a stale token, and the RM logs the SASL exceptions over and over. -- 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