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

Posted to yarn-issues@hadoop.apache.org by "Junping Du (JIRA)" <ji...@apache.org> on 2015/05/01 17:58:06 UTC

[jira] [Commented] (YARN-950) Ability to limit or avoid aggregating logs beyond a certain size

    [ https://issues.apache.org/jira/browse/YARN-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523363#comment-14523363 ] 

Junping Du commented on YARN-950:
---------------------------------

+1 on the idea of limiting the size of log aggregation. We should have someway to truncate (front & tail) the log contents if it is really large.

> Ability to limit or avoid aggregating logs beyond a certain size
> ----------------------------------------------------------------
>
>                 Key: YARN-950
>                 URL: https://issues.apache.org/jira/browse/YARN-950
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>    Affects Versions: 0.23.9, 2.6.0
>            Reporter: Jason Lowe
>
> It would be nice if ops could configure a cluster such that any container log beyond a configured size would either only have a portion of the log aggregated or not aggregated at all.  This would help speed up the recovery path for cases where a container creates an enormous log and fills a disk, as currently it tries to aggregate the entire, enormous log rather than only aggregating a small portion or simply deleting it.



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