[
https://issues.apache.org/jira/browse/YARN-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708694#comment-14708694
]
Hudson commented on YARN-221:
-----------------------------
SUCCESS: Integrated in Hadoop-Mapreduce-trunk-Java8 #297 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/297/])
YARN-221. Addendum patch to compilation issue which is caused by missing
(xgong: rev b71c6006f579ac6f0755975a9b908b0062618b46)
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/logaggregation/AllContainerLogAggregationPolicy.java
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/logaggregation/ContainerLogsRetentionPolicy.java
> 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: log-aggregation, nodemanager
> Reporter: Robert Joseph Evans
> Assignee: Ming Ma
> Fix For: 2.8.0
>
> Attachments: YARN-221-6.patch, YARN-221-7.patch, YARN-221-8.patch,
> YARN-221-9.patch, YARN-221-addendum.1.patch, YARN-221-trunk-v1.patch,
> YARN-221-trunk-v2.patch, YARN-221-trunk-v3.patch, YARN-221-trunk-v4.patch,
> YARN-221-trunk-v5.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
