[
https://issues.apache.org/jira/browse/MAPREDUCE-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497506#comment-13497506
]
Hadoop QA commented on MAPREDUCE-4797:
--------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12553564/MAPREDUCE-4797.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3031//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3031//console
This message is automatically generated.
> 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
