[MAPREDUCE-4797] LocalContainerAllocator can loop forever trying to contact the RM

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.23.3, 2.0.1-alpha
• Fix Version/s: 2.0.3-alpha, 0.23.5
• Component/s: applicationmaster
• Target Version/s: 2.0.3-alpha, 0.23.5
• Assignee: Jason Darrell Lowe
• Reporter: Jason Darrell Lowe
• Created: 14/Nov/12 02:15
• Updated: 03/Sep/14 23:17
• Resolved: 14/Nov/12 23:09

Description

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.