cluster.YarnScheduler

Lost executor 2 on quickstart.cloudera: Container marked as failed: container_1485279684410_0003_02_000003 on host: quickstart.cloudera. Exit status: 50. Diagnostics: Exception from container-launch. Container id: container_1485279684410_0003_02_000003 Exit code: 50 Stack trace: ExitCodeException exitCode=50:

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web22

  • Lost executor 2 on quickstart.cloudera: Container marked as failed: container_1485279684410_0003_02_000003 on host: quickstart.cloudera. Exit status: 50. Diagnostics: Exception from container-launch. Container id: container_1485279684410_0003_02_000003 Exit code: 50 Stack trace: ExitCodeException exitCode=50:
  • Lost executor 12 on xxxx11095hw2288.hadoop.ny2.xxxxcorp.com: Container marked as failed: container_e19_1475054520611_4318873_01_000015 on host: xxxx11095hw2288.hadoop.ny2.xxxxcorp.com. Exit status: 50. Diagnostics: Exception from container-launch. Container id: container_e19_1475054520611_4318873_01_000015 Exit code: 50 Stack trace: ExitCodeException exitCode=50:
  • via cloudera.com by Unknown author, 7 months ago
    Lost executor 18 on totoro.akainix.local: Container marked as failed: container_1468247436212_0003_01_000019 on host: totoro.akainix.local. Exit status: 50. Diagnostics: Exception from container-launch. Container id: container_1468247436212_0003_01_000019 Exit code: 50 Stack trace: ExitCodeException exitCode=50:
  • Stack trace

    • cluster.YarnScheduler: Lost executor 2 on quickstart.cloudera: Container marked as failed: container_1485279684410_0003_02_000003 on host: quickstart.cloudera. Exit status: 50. Diagnostics: Exception from container-launch. Container id: container_1485279684410_0003_02_000003 Exit code: 50 Stack trace: ExitCodeException exitCode=50: at org.apache.hadoop.util.Shell.runCommand(Shell.java:578) at org.apache.hadoop.util.Shell.run(Shell.java:481) at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:763) at org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.launchContainer(DefaultContainerExecutor.java:213) at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:302) at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:82) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.