Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9C7EE18B3B for ; Tue, 8 Mar 2016 14:53:41 +0000 (UTC) Received: (qmail 9153 invoked by uid 500); 8 Mar 2016 14:53:41 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 9099 invoked by uid 500); 8 Mar 2016 14:53:41 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 8969 invoked by uid 99); 8 Mar 2016 14:53:41 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Mar 2016 14:53:41 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id DCDBC2C1F58 for ; Tue, 8 Mar 2016 14:53:40 +0000 (UTC) Date: Tue, 8 Mar 2016 14:53:40 +0000 (UTC) From: "Jason Lowe (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-4771) Some containers can be skipped during log aggregation after NM restart MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)