hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan Roberts (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4834) ProcfsBasedProcessTree doesn't track daemonized processes
Date Tue, 05 Apr 2016 15:08:25 GMT

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

Nathan Roberts updated YARN-4834:
---------------------------------
    Attachment: YARN-4834.001.patch

Simple fix that falls back to sessionID if process has become owned by init. Seemed safest
low risk change.

Other options might be:
- Only use sessionID to build process tree
- Use container cgroup (cgroup.procs) if available/configured.

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

Mime
View raw message