[
https://issues.apache.org/jira/browse/YARN-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated YARN-7087:
-----------------------------
Priority: Blocker (was: Critical)
Increasing severity to Blocker since this is not that rare when apps are killed
and logs are getting lost when it happens.
> NM failed to perform log aggregation due to absent container
> ------------------------------------------------------------
>
> Key: YARN-7087
> URL: https://issues.apache.org/jira/browse/YARN-7087
> Project: Hadoop YARN
> Issue Type: Bug
> Components: log-aggregation
> Affects Versions: 2.8.1
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Priority: Blocker
> Attachments: YARN-7087.001.patch, YARN-7087.002.patch
>
>
> Saw a case where the NM failed to aggregate the logs for a container because
> it claimed it was absent:
> {noformat}
> 2017-08-23 18:35:38,283 [AsyncDispatcher event handler] WARN
> logaggregation.LogAggregationService: Log aggregation cannot be started for
> container_e07_1503326514161_502342_01_000001, as its an absent container
> {noformat}
> Containers should not be allowed to disappear if they're not done being fully
> processed by the NM.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
