Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 78CAD10CE4 for ; Mon, 28 Oct 2013 08:48:35 +0000 (UTC) Received: (qmail 51044 invoked by uid 500); 28 Oct 2013 08:48:34 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 50874 invoked by uid 500); 28 Oct 2013 08:48:33 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 50848 invoked by uid 99); 28 Oct 2013 08:48:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Oct 2013 08:48:33 +0000 Date: Mon, 28 Oct 2013 08:48:33 +0000 (UTC) From: "haosdent (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-1109) Consider throttling or demoting NodeManager "Sending out status for container" logs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent updated YARN-1109: --------------------------- Attachment: (was: YARN-1109.patch) > Consider throttling or demoting NodeManager "Sending out status for container" logs > ----------------------------------------------------------------------------------- > > Key: YARN-1109 > URL: https://issues.apache.org/jira/browse/YARN-1109 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager > Affects Versions: 2.1.0-beta > Reporter: Sandy Ryza > Assignee: haosdent > Labels: newbie > Attachments: YARN-1109.patch > > > Diagnosing NodeManager and container launch problems is made more difficult by the enormous number of logs like > {code} > Sending out status for container: container_id {, app_attempt_id {, application_id {, id: 18, cluster_timestamp: 1377559361179, }, attemptId: 1, }, id: 1337, }, state: C_RUNNING, diagnostics: "Container killed by the ApplicationMaster.\n", exit_status: -1000 > {code} > On an NM with a few containers I am seeing tens of these per second. -- This message was sent by Atlassian JIRA (v6.1#6144)