[
https://issues.apache.org/jira/browse/MAPREDUCE-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497493#comment-13497493
]
Robert Joseph Evans commented on MAPREDUCE-4797:
------------------------------------------------
The code looks good to me. My only comment is with the test. If a different
exception is thrown, that exception is eaten and it is likely to be difficult
to debug the error. If you could log it some how that would be great.
> 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
> Attachments: 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
