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 "Konstantin Shvachko (JIRA)" <ji...@apache.org> on 2017/05/05 00:37:04 UTC
[jira] [Updated] (YARN-4771) Some containers can be skipped during
log aggregation after NM restart
[ https://issues.apache.org/jira/browse/YARN-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Shvachko updated YARN-4771:
--------------------------------------
Priority: Major (was: Critical)
Changing to Major to remove from the scope of 2.7.4 release.
Feel free to add back if you plan to fix it.
> 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, YARN-4771.002.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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org