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

yarn service application stops when AM is killed with SIGTERM

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete CommentsDelete
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.2.0, 3.1.1
    • yarn-native-services
    • None

    Description

      Steps:

      1) Launch sleeper job ( non-docker yarn service)

      
      RUNNING: /usr/hdp/current/hadoop-yarn-client/bin/yarn app -launch fault-test-am-sleeper /usr/hdp/current/hadoop-yarn-client/yarn-service-examples/sleeper/sleeper.json
      
      WARNING: YARN_LOG_DIR has been replaced by HADOOP_LOG_DIR. Using value of YARN_LOG_DIR.
      
      WARNING: YARN_LOGFILE has been replaced by HADOOP_LOGFILE. Using value of YARN_LOGFILE.
      
      WARNING: YARN_PID_DIR has been replaced by HADOOP_PID_DIR. Using value of YARN_PID_DIR.
      
      WARNING: YARN_OPTS has been replaced by HADOOP_OPTS. Using value of YARN_OPTS.
      
      18/04/06 22:24:24 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
      
      18/04/06 22:24:24 INFO client.AHSProxy: Connecting to Application History server at xxx:10200
      
      18/04/06 22:24:24 INFO client.AHSProxy: Connecting to Application History server at xxx:10200
      
      18/04/06 22:24:24 INFO client.ApiServiceClient: Loading service definition from local FS: /usr/hdp/current/hadoop-yarn-client/yarn-service-examples/sleeper/sleeper.json
      
      18/04/06 22:24:26 INFO util.log: Logging initialized @3631ms
      
      18/04/06 22:24:37 INFO client.ApiServiceClient: Application ID: application_1522887500374_0010
      
      Exit Code: 0

      2) Wait for sleeper component to be up

      3) Kill AM process PID

       

      Expected behavior:

      New attempt of AM will be started. The pre-existing container will keep running

       

      Actual behavior:

      Application finishes with State : FINISHED and Final-State : ENDED

      New attempt was never launched

      Note: 

      when the AM gets a SIGTERM and gracefully shuts itself down. It is shutting the entire app down instead of letting it continue to run for another attempt

       

      Attachments

        Activity

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

          People

            billie Billie Rinaldi Assign to me
            yeshavora Yesha Vora
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment