From mapreduce-dev-return-8321-apmail-hadoop-mapreduce-dev-archive=hadoop.apache.org@hadoop.apache.org Fri Sep 21 18:05:09 2012 Return-Path: X-Original-To: apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2F2B5D346 for ; Fri, 21 Sep 2012 18:05:09 +0000 (UTC) Received: (qmail 22155 invoked by uid 500); 21 Sep 2012 18:05:08 -0000 Delivered-To: apmail-hadoop-mapreduce-dev-archive@hadoop.apache.org Received: (qmail 21997 invoked by uid 500); 21 Sep 2012 18:05:07 -0000 Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-dev@hadoop.apache.org Delivered-To: mailing list mapreduce-dev@hadoop.apache.org Received: (qmail 21743 invoked by uid 99); 21 Sep 2012 18:05:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Sep 2012 18:05:07 +0000 Date: Sat, 22 Sep 2012 05:05:07 +1100 (NCT) From: "Chris Riccomini (JIRA)" To: mapreduce-dev@hadoop.apache.org Message-ID: <2003495728.108610.1348250707681.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (MAPREDUCE-4672) RM with lost NMs results in massive log of AppAttemptId doesnt exist in cache MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Chris Riccomini created MAPREDUCE-4672: ------------------------------------------ Summary: RM with lost NMs results in massive log of AppAttemptId doesnt exist in cache Key: MAPREDUCE-4672 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4672 Project: Hadoop Map/Reduce Issue Type: Bug Components: resourcemanager Affects Versions: 0.23.1 Reporter: Chris Riccomini Hey Guys, I'm running a 9 node cluster with 8 NMs and a single RM node. If I run an app master and have that app master start a container, then shut down all nodes (to simulate a complete failure), the containers timeout and fail, as expected. What's unexpected is that my log then starts filling with: 2012-09-21 18:02:02,614 ERROR resourcemanager.ApplicationMasterService (ApplicationMasterService.java:allocate(247)) - AppAttemptId doesnt exist in cache appattempt_1348248013002_0001_000001 2012-09-21 18:02:03,617 ERROR resourcemanager.ApplicationMasterService (ApplicationMasterService.java:allocate(247)) - AppAttemptId doesnt exist in cache appattempt_1348248013002_0001_000001 2012-09-21 18:02:04,618 ERROR resourcemanager.ApplicationMasterService (ApplicationMasterService.java:allocate(247)) - AppAttemptId doesnt exist in cache appattempt_1348248013002_0001_000001 2012-09-21 18:02:05,620 ERROR resourcemanager.ApplicationMasterService (ApplicationMasterService.java:allocate(247)) - AppAttemptId doesnt exist in cache appattempt_1348248013002_0001_000001 2012-09-21 18:02:06,621 ERROR resourcemanager.ApplicationMasterService (ApplicationMasterService.java:allocate(247)) - AppAttemptId doesnt exist in cache appattempt_1348248013002_0001_000001 2012-09-21 18:02:07,623 ERROR resourcemanager.ApplicationMasterService (ApplicationMasterService.java:allocate(247)) - AppAttemptId doesnt exist in cache appattempt_1348248013002_0001_000001 2012-09-21 18:02:08,624 ERROR resourcemanager.ApplicationMasterService (ApplicationMasterService.java:allocate(247)) - AppAttemptId doesnt exist in cache appattempt_1348248013002_0001_000001 Is there any way to shut this off/fix it? It just keeps going forever, until I bounce the RM node. Thanks! Chris -- 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