[jira] [Updated] (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:all-tabpanel ] Junping Du updated YARN-950: Affects Version/s: 2.6.0 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)
[jira] [Updated] (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:all-tabpanel ] Junping Du updated YARN-950: Issue Type: Sub-task (was: Improvement) Parent: YARN-431 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: Sub-task Components: log-aggregation, 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)
[jira] [Updated] (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:all-tabpanel ] Junping Du updated YARN-950: Component/s: log-aggregation 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: log-aggregation, 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)