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

MR AM dies badly when Node is decomissioned

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 0.23.3, 2.0.0-alpha, 3.0.0-alpha1
    • Fix Version/s: 0.23.3, 2.0.2-alpha
    • Component/s: None
    • Labels:
      None

      Description

      The MR AM always thinks that it is being killed by the RM when it gets a kill signal and it has not finished processing yet. In reality the RM kill signal is only sent when the client cannot communicate directly with the AM, which probably means that the AM is in a bad state already. The much more common case is that the node is marked as unhealthy or decomissioned.

      I propose that in the short term the AM will only clean up if

      1. The process has been asked by the client to exit (kill)
      2. The process job has finished cleanly and is exiting already
      3. This is that last retry of the AM retries.

      The downside here is that the .staging directory will be leaked and the job will not show up in the history server on an kill from the RM in some cases.

      At least until the full set of AM cleanup issues can be addressed, probably as part of MAPREDUCE-4428

        Attachments

          Activity

          $i18n.getText('security.level.explanation', $currentSelection) Viewable by All Users
          Cancel

            People

            • Assignee:
              revans2 Robert Joseph Evans Assign to me
              Reporter:
              revans2 Robert Joseph Evans

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment