hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (YARN-3759) Include command line, localization info and env vars on AM launch failure
Date Mon, 08 Jun 2015 12:27:01 GMT

     [ https://issues.apache.org/jira/browse/YARN-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Steve Loughran resolved YARN-3759.
----------------------------------
    Resolution: Duplicate

> Include command line, localization info and env vars on AM launch failure
> -------------------------------------------------------------------------
>
>                 Key: YARN-3759
>                 URL: https://issues.apache.org/jira/browse/YARN-3759
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>    Affects Versions: 2.7.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> While trying to diagnose AM launch failures, its important to be able to get at the final,
expanded {{CLASSPATH}} and other env variables. We don't get that today: you can log the unexpanded
values on the client, and tweak NM ContainerExecutor log levels to DEBUG & get some of
this —‚ut you don't get it in the task logs, and tuning NM log level isn't viable on a
large, busy cluster.
> Launch failures should include some env specifics:
> # list of env vars (ideally, full getenv values), with some stripping of "sensitive"
options (i'm thinking AWS env vars here)
> # command line
> # path localisations
> These can go in the task logs, we don't need to include them in the application report.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message