[
https://issues.apache.org/jira/browse/YARN-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13909440#comment-13909440
]
Ming Ma commented on YARN-221:
------------------------------
One thing to add we need the definition and policy on how to handle those tasks
that are in the finishing state and MR AM ends up stopping them as they don't
exit by themselves. From customers's point of view, the task is considered to
be successful. For log aggregation point of view, if we want to aggregate only
failed task, then MR AM still needs to tell NM not to do log aggregation for
such kind of tasks. Maybe this isn't important if we believe most of the tasks
will exit by themselves. But it is still useful to provide the proper
definition and policy for it.
> 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
> Reporter: Robert Joseph Evans
> Assignee: Chris Trezzo
> Attachments: YARN-221-trunk-v1.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.1.5#6160)
