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

Delays are noticed to launch docker container

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.1
    • Fix Version/s: 3.3.0
    • Component/s: None
    • Labels:
    • Target Version/s:
    • Release Note:
      add "docker inspect" retries to discover container exit code.

      Description

      Launch dshell application. Wait for application to go in RUNNING state.

      yarn  jar /xx/hadoop-yarn-applications-distributedshell-*.jar  -shell_command "sleep 300" -num_containers 1 -shell_env YARN_CONTAINER_RUNTIME_TYPE=docker -shell_env YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=httpd:0.1 -shell_env YARN_CONTAINER_RUNTIME_DOCKER_DELAYED_REMOVAL=true -jar /usr/hdp/current/hadoop-yarn-client/hadoop-yarn-applications-distributedshell-xx.jar
      

      Find out container allocation. Run docker inspect command for docker containers launched by app.

      Sometimes, the container is allocated to NM but docker PID is not up.

      Command ssh -q -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null xxx "sudo su - -c \"docker ps  -a | grep container_e02_1531189225093_0003_01_000002\" root" failed after 0 retries 
      

        Attachments

        1. YARN-8587.patch
          2 kB
          dockerzhang

          Activity

            People

            • Assignee:
              Charo Zhang dockerzhang
              Reporter:
              yeshavora Yesha Vora
            • Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: