[
https://issues.apache.org/jira/browse/YARN-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated YARN-4771:
-----------------------------
Attachment: YARN-4771.001.patch
Simple patch which preserves the container as long as the application is still
active, and that should solve the reported problem. However it may have issues
with very long-running apps that churn a lot of containers, since the container
state won't be released until the application completes.
> Some containers can be skipped during log aggregation after NM restart
> ----------------------------------------------------------------------
>
> Key: YARN-4771
> URL: https://issues.apache.org/jira/browse/YARN-4771
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 2.7.2
> Reporter: Jason Lowe
> Attachments: YARN-4771.001.patch
>
>
> A container can be skipped during log aggregation after a work-preserving
> nodemanager restart if the following events occur:
> # Container completes more than
> yarn.nodemanager.duration-to-track-stopped-containers milliseconds before the
> restart
> # At least one other container completes after the above container and before
> the restart
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
