[
https://issues.apache.org/jira/browse/MAPREDUCE-6401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589538#comment-14589538
]
Devaraj K commented on MAPREDUCE-6401:
--------------------------------------
The attached log seems to be MRAppMaster log(not the task logs), where you
could see overall MR Job(all the tasks) logs.
bq. I'm trying to fix it blindfolded.
I understand that these logs can be improved further to get the detailed failed
information instead of just exit codes. If you want to know the reason for
container launch failure, you can check the corresponding failed container/task
log by going to Job History Server UI(if log aggregation enabled) or directly
by going to the app log dir’s for the container stderr/stdout in the failed
node.
> Container-launch failure gives no debugging output
> --------------------------------------------------
>
> Key: MAPREDUCE-6401
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6401
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.6.0
> Environment: HDP 2.2
> Reporter: Hari Sekhon
> Attachments: job.log
>
>
> MR jobs are failing on my cluster with Stack trace: ExitCodeException
> exitCode=7 but little else in terms of debugging information. Can we please
> improve the debugging info? Log file is attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
