You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-dev@hadoop.apache.org by "Xuan Gong (JIRA)" <ji...@apache.org> on 2015/06/09 01:51:01 UTC

[jira] [Resolved] (YARN-1377) Log aggregation via node manager should expose expose a way to cancel log aggregation at application or container level

     [ https://issues.apache.org/jira/browse/YARN-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xuan Gong resolved YARN-1377.
-----------------------------
    Resolution: Duplicate

> Log aggregation via node manager should expose expose a way to cancel log aggregation at application or container level
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-1377
>                 URL: https://issues.apache.org/jira/browse/YARN-1377
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Omkar Vinit Joshi
>            Assignee: Xuan Gong
>
> Today when application finishes it starts aggregating all the logs but that may slow down the whole process significantly...
> there can be situations where certain containers overwrote the logs .. say in multiple GBs....in these scenarios we need a way to cancel log aggregation for certain containers. These can be at per application level or at per container level.
> thoughts?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)