Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-dev@hadoop.apache.org
Date: Tue, 27 Aug 2013 23:45:53 +0000 (UTC)
From: "Sandy Ryza (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.12665821.1377647151425.43862.1377647153406@arcas>
In-Reply-To: <JIRA.12665821.1377647151425@arcas>
References: <JIRA.12665821.1377647151425@arcas>
Subject: [jira] [Created] (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

Sandy Ryza created YARN-1109:
--------------------------------

             Summary: 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


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 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