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

AM should explicity exit JVM after all services have stopped

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

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.5.0
    • 2.8.0, 3.0.0-alpha1
    • None
    • None
    • Reviewed

    Description

      Occasionally the MapReduce AM can "get stuck" trying to shut down. MAPREDUCE-6049 and MAPREDUCE-5888 were specific instances that have been fixed, but this can also occur with uber jobs if the task code inadvertently leaves non-daemon threads lingering.

      We should explicitly shutdown the JVM after the MapReduce AM has unregistered and all services have been stopped.

      Attachments

        1. MAPREDUCE-6279.v1.txt
          1 kB
          Eric Payne
        2. MAPREDUCE-6279.v2.txt
          6 kB
          Eric Payne
        3. MAPREDUCE-6279.v3.patch
          6 kB
          Eric Payne
        4. MAPREDUCE-6279.v4.patch
          6 kB
          Eric Payne

        Activity

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

          People

            epayne Eric Payne
            jlowe Jason Darrell Lowe
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment