Uploaded image for project: 'Hadoop Map/Reduce'
  1. Hadoop Map/Reduce
  2. MAPREDUCE-3240

NM should send a SIGKILL for completed containers also

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 0.23.0
    • 0.23.0
    • mrv2, nodemanager
    • None
    • Reviewed

    Description

      This is to address the containers which exit properly after spawning sub-processes themselves. We don't want to leave these sub-process-tree or else they can pillage the NM's resources.

      Today, we already have code to send SIGKILL to the whole process-trees (because of single sessionId resulting from setsid) when the container is alive. We need to obtain the PID of the containers when they start and use that PID to send signal for completed containers' case also.

      Attachments

        1. MR-3240.wip.patch
          37 kB
          Hitesh Shah
        2. MR-3240.1.patch
          58 kB
          Hitesh Shah
        3. MR-3240.2.patch
          60 kB
          Hitesh Shah
        4. MR-3240.3.patch
          60 kB
          Hitesh Shah
        5. MR-3240.4.wip.patch
          63 kB
          Hitesh Shah
        6. MR-3240.5.patch
          67 kB
          Hitesh Shah
        7. MAPREDUCE-3240-20111027.1.txt
          72 kB
          Vinod Kumar Vavilapalli
        8. MAPREDUCE-3240-20111027.2.txt
          74 kB
          Vinod Kumar Vavilapalli

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MAPREDUCE-3260 Yarn app stuck in KILL_WAIT state

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. MAPREDUCE-3084 race when KILL_CONTAINER is received for a LOCALIZED container

          • Blocker - Blocks development and/or testing work, production could not run
          • Closed

          Activity

            People

              hitesh Hitesh Shah
              vinodkv Vinod Kumar Vavilapalli
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: