Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 16 Nov 2012 18:46:12 +0000 (UTC)
From: "Robert Joseph Evans (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <1341440470.125288.1353091572378.JavaMail.jiratomcat@arcas>
Subject: [jira] [Created] (YARN-221) NM should provide a way for AM to tell
 it not to aggregate logs.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Robert Joseph Evans created YARN-221:
----------------------------------------

             Summary: NM should provide a way for AM to tell it not to aggregate logs.
                 Key: YARN-221
                 URL: https://issues.apache.org/jira/browse/YARN-221
             Project: Hadoop YARN
          Issue Type: Sub-task
          Components: nodemanager
    Affects Versions: 0.23.4
            Reporter: Robert Joseph Evans


The NodeManager should provide a way for an AM to tell it that either the logs should not be aggregated, that they should be aggregated with a high priority, or that they should be aggregated but with a lower priority.  The AM should be able to do this in the ContainerLaunch context to provide a default value, but should also be able to update the value when the container is released.

This would allow for the NM to not aggregate logs in some cases, and avoid connection to the NN at all.

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