hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4771) Some containers can be skipped during log aggregation after NM restart
Date Mon, 14 Mar 2016 17:50:33 GMT

     [ https://issues.apache.org/jira/browse/YARN-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod Kumar Vavilapalli updated YARN-4771:
------------------------------------------
    Priority: Critical  (was: Major)

Sounds bad given also the high possibility of leak on the file-system with non-aggregated
/ non-deleted container-logs, bumping priority.

> 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
>            Priority: Critical
>         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.4#6332)

Mime
View raw message