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 "Nathan Roberts (JIRA)" <ji...@apache.org> on 2016/04/05 17:12:25 UTC

[jira] [Commented] (YARN-4834) ProcfsBasedProcessTree doesn't track daemonized processes

    [ 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)