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

[Submarine] Submarine job will fail to run as a first job on a new created Hadoop 3.2.0 RC1 cluster

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      This issue was found when verifying submarine in Hadoop 3.2.0 RC1 planning. The reproduce steps are:

      1. Init a new HDFS and YARN (LinuxContainerExecutor and Docker enabled)
      2. Before run any other yarn service job, use yarn user to submit a submarine job

      The job will fail with below error:

       

      LogType:serviceam-err.txt
      LogLastModifiedTime:Thu Jan 10 21:15:23 +0800 2019
      LogLength:86
      LogContents:
      Error: Could not find or load main class org.apache.hadoop.yarn.service.ServiceMaster
      End of LogType:serviceam-err.txt
      

      This seems because the dependencies are not ready as the service client reported:

      2019-01-10 21:50:47,380 WARN client.ServiceClient: Property yarn.service.framework.path has a value /yarn-services/3.2.0/service-dep.tar.gz, but is not a valid file
      2019-01-10 21:50:47,381 INFO client.ServiceClient: Uploading all dependency jars to HDFS. For faster submission of apps, set config property yarn.service.framework.path to the dependency tarball location. Dependency tarball can be uploaded to any HDFS path directly or by using command: yarn app -enableFastLaunch [<Destination Folder>]

       

      When this error happens, I found that there is no “/yarn-services” directory created in HDFS.

      But after I run “yarn app -launch my-sleeper sleeper”, the “/yarn-services” created in HDFS and then the submarine job can run successfully.

      yarn@master0-VirtualBox:~/apache-hadoop-install-dir/hadoop-dev-workspace$ hdfs dfs -ls /yarn-services/3.2.0/*
      -rwxr-xr-x 1 yarn supergroup 93596476 2019-01-11 08:23 /yarn-services/3.2.0/service-dep.tar.gz

      It seems an issue of yarn service in 3.2.0 RC1 and I files this Jira to track it.

       

      And verified that trunk branch doesn't have this issue.

      Attachments

        Activity

          People

            sunilg Sunil G
            tangzhankun Zhankun Tang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: