Return-Path: 
 <yarn-issues-return-83028-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org>
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 44D1E1910F
	for <apmail-hadoop-yarn-issues-archive@minotaur.apache.org>;
 Tue,  5 Apr 2016 15:12:26 +0000 (UTC)
Received: (qmail 41023 invoked by uid 500); 5 Apr 2016 15:12:25 -0000
Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org
Received: (qmail 40950 invoked by uid 500); 5 Apr 2016 15:12:25 -0000
Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:yarn-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:yarn-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:yarn-issues@hadoop.apache.org>
List-Id: <yarn-issues.hadoop.apache.org>
Reply-To: yarn-issues@hadoop.apache.org
Delivered-To: mailing list yarn-issues@hadoop.apache.org
Received: (qmail 40597 invoked by uid 99); 5 Apr 2016 15:12:25 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Apr 2016 15:12:25 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 8F7C62C1F64
	for <yarn-issues@hadoop.apache.org>; Tue,  5 Apr 2016 15:12:25 +0000 (UTC)
Date: Tue, 5 Apr 2016 15:12:25 +0000 (UTC)
From: "Nathan Roberts (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12951255.1458231654000.139151.1459869145584@Atlassian.JIRA>
In-Reply-To: <JIRA.12951255.1458231654000@Atlassian.JIRA>
References: <JIRA.12951255.1458231654000@Atlassian.JIRA>
 <JIRA.12951255.1458231654250@arcas>
Subject: [jira] [Commented] (YARN-4834) ProcfsBasedProcessTree doesn't track
 daemonized processes
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-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226424#comment-15226424 ] 

Nathan Roberts commented on YARN-4834:
--------------------------------------

As a note, we were seeing this with slider applications. I didn't investigate far enough to know if all slider applications escape or if this was just a a characteristic of this particular application.

> ProcfsBasedProcessTree doesn't track daemonized processes
> ---------------------------------------------------------
>
>                 Key: YARN-4834
>                 URL: https://issues.apache.org/jira/browse/YARN-4834
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 3.0.0, 2.7.2
>            Reporter: Nathan Roberts
>            Assignee: Nathan Roberts
>         Attachments: YARN-4834.001.patch
>
>
> Currently the algorithm uses ppid from /proc/<pid>/stat which can be 1 if a child process has daemonized itself. This causes potentially large processes from not being monitored. 
> session id might be a better choice since that's what we use to signal the container during teardown. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)