[
https://issues.apache.org/jira/browse/YARN-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suma Shivaprasad updated YARN-6550:
-----------------------------------
Attachment: YARN-6550.009.patch
Attached updated patch with changes to
a. Remove stack trace which doesnt add anything useful for debugging purposes
************************************ Before
************************************
{noformat}
2017-08-18 14:27:35,350 INFO mapreduce.Job: Job job_1503091623633_0001 failed
with state FAILED due to: Application application_1503091623633_0001 failed 2
times due to AM Container for appattempt_1503091623633_0001_000002 exited with
exitCode: 64
Failing this attempt.Diagnostics: [2017-08-18 14:27:34.601]Exception from
container-launch.
Container id: container_1503091623633_0001_02_000001
Exit code: 64
Exception message: mkdir: illegal option -- j
usage: mkdir [-pv] [-m mode] directory ...
Stack trace: ExitCodeException exitCode=64: mkdir: illegal option -- j
usage: mkdir [-pv] [-m mode] directory ...
at org.apache.hadoop.util.Shell.runCommand(Shell.java:994)
at org.apache.hadoop.util.Shell.run(Shell.java:887)
at
org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:1212)
at
org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.launchContainer(DefaultContainerExecutor.java:295)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.launchContainer(ContainerLaunch.java:460)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:280)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:90)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
[2017-08-18 14:27:34.601]
[2017-08-18 14:27:34.602]Container exited with a non-zero exit code 64.
[2017-08-18 14:27:34.603]
[2017-08-18 14:27:34.603]Container exited with a non-zero exit code 64.
[2017-08-18 14:27:34.603]
For more detailed output, check the application tracking page:
http://0.0.0.0:8188/applicationhistory/app/application_1503091623633_0001 Then
click on links to logs of each attempt.
. Failing the application.
2017-08-18 14:27:35,369 INFO mapreduce.Job: Counters: 0
{noformat}
************************************ After patch
************************************
{noformat}
Failing this attempt.Diagnostics: [2017-08-18 14:18:10.318]Exception from
container-launch.
Container id: container_1503091074428_0001_02_000001
Exit code: 64
[2017-08-18 14:18:10.318]
[2017-08-18 14:18:10.320]Container exited with a non-zero exit code 64. Error
file: prelaunch.err.
Last 4096 bytes of prelaunch.err :
mkdir: illegal option -- j
usage: mkdir [-pv] [-m mode] directory ...
[2017-08-18 14:18:10.321]
[2017-08-18 14:18:10.321]Container exited with a non-zero exit code 64. Error
file: prelaunch.err.
Last 4096 bytes of prelaunch.err :
mkdir: illegal option -- j
usage: mkdir [-pv] [-m mode] directory ...
[2017-08-18 14:18:10.321]
For more detailed output, check the application tracking page:
http://0.0.0.0:8188/applicationhistory/app/application_1503091074428_0001 Then
click on links to logs of each attempt.
. Failing the application.
2017-08-18 14:18:11,219 INFO mapreduce.Job: Counters: 0
{noformat}
b. Addressed Allen's review comments to add [ and quotes in error checks
> Capture launch_container.sh logs
> --------------------------------
>
> Key: YARN-6550
> URL: https://issues.apache.org/jira/browse/YARN-6550
> Project: Hadoop YARN
> Issue Type: Sub-task
> Affects Versions: 3.0.0-beta1
> Reporter: Wangda Tan
> Assignee: Suma Shivaprasad
> Attachments: YARN-6550.002.patch, YARN-6550.003.patch,
> YARN-6550.005.patch, YARN-6550.006.patch, YARN-6550.007.patch,
> YARN-6550.008.patch, YARN-6550.009.patch, YARN-6550.patch
>
>
> launch_container.sh which generated by NM will do a bunch of things (like
> create link, etc.) while launch a process. No logs captured until {{exec}} is
> called. We need capture all failures of launch_container.sh for easier
> troubleshooting.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
