[
https://issues.apache.org/jira/browse/YARN-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269162#comment-15269162
]
Hudson commented on YARN-4834:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9707 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9707/])
YARN-4834. ProcfsBasedProcessTree doesn't track daemonized processes. (jlowe:
rev c6b48391680c1b81a86aabc3ad4c725bfade6d2e)
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/ProcfsBasedProcessTree.java
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/util/TestProcfsBasedProcessTree.java
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
