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

Diagnostic message should improve when yarn service fails to launch due to ATS unavailability

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.0
    • Fix Version/s: 3.2.0, 3.1.1
    • Component/s: yarn-native-services
    • Labels:
      None

      Description

      Scenario:

      1) shutdown ATS
      2) launch yarn service.

      yarn service launch cmd fails with below stack trace. There is no diagnostic message available in response.

      bash-4.2$ yarn app -launch hbase-sec /tmp/hbase-secure.yar 
      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.
      18/05/17 13:24:43 INFO client.RMProxy: Connecting to ResourceManager at xxx/xxx:8050
      18/05/17 13:24:44 INFO client.AHSProxy: Connecting to Application History server at localhost/xxx:10200
      18/05/17 13:24:44 INFO client.RMProxy: Connecting to ResourceManager at xxx/xxx:8050
      18/05/17 13:24:44 INFO client.AHSProxy: Connecting to Application History server at localhost/127.0.0.1:10200
      18/05/17 13:24:44 INFO client.ApiServiceClient: Loading service definition from local FS: /tmp/hbase-secure.yar
      18/05/17 13:26:06 ERROR client.ApiServiceClient: 
      bash-4.2$ echo $?
      56

      The Error message should provide ConnectionRefused exception.

        Attachments

          Activity

            People

            • Assignee:
              billie.rinaldi Billie Rinaldi
              Reporter:
              yeshavora Yesha Vora
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: