Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-4834

ProcfsBasedProcessTree doesn't track daemonized processes

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.7.2, 3.0.0-alpha1
    • 2.8.0, 2.7.3, 3.0.0-alpha1
    • nodemanager
    • None
    • Reviewed

    Description

      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.

      Attachments

        1. YARN-4834.001.patch
          6 kB
          Nathan Roberts

        Issue Links

        is required by

        Improvement - An improvement or enhancement to an existing feature or task. YARN-5202 Dynamic Overcommit of Node Resources - POC

        • Major - Major loss of function.
        • Open
        relates to

        Test - A new unit, integration or system test. YARN-6763 TestProcfsBasedProcessTree#testProcessTree fails in trunk

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Open

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            nroberts Nathan Roberts
            nroberts Nathan Roberts
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment