Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Wed, 14 Nov 2012 02:16:12 +0000 (UTC)
From: "Jason Lowe (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <556954673.111596.1352859372504.JavaMail.jiratomcat@arcas>
Subject: [jira] [Created] (MAPREDUCE-4797) LocalContainerAllocator can loop
 forever trying to contact the RM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jason Lowe created MAPREDUCE-4797:
-------------------------------------

             Summary: 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: 2.0.1-alpha, 0.23.3
            Reporter: Jason Lowe


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