hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-814) Difficult to diagnose a failed container launch when error due to invalid environment variable
Date Thu, 18 Jul 2013 00:10:49 GMT

    [ https://issues.apache.org/jira/browse/YARN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13711828#comment-13711828
] 

Jian He commented on YARN-814:
------------------------------

bq. When an exception happens in LinuxContainerExecutor.startLocalizer(), the exception's
message eventually is set as diagnostics at ResourceLocalizationService.LocalizerRunner.run()(+996-+997).
But the shell output is lost. Can you consistently fix this?
The patch should already handle this.
bq. deleteAsUser errors are missing too, but I remember there's a separate ticket
will do this in a separate ticket

Other comments fixed
                
> Difficult to diagnose a failed container launch when error due to invalid environment
variable
> ----------------------------------------------------------------------------------------------
>
>                 Key: YARN-814
>                 URL: https://issues.apache.org/jira/browse/YARN-814
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Hitesh Shah
>            Assignee: Jian He
>         Attachments: YARN-814.1.patch, YARN-814.2.patch, YARN-814.3.patch, YARN-814.4.patch,
YARN-814.5.patch, YARN-814.6.patch, YARN-814.patch
>
>
> The container's launch script sets up environment variables, symlinks etc. 
> If there is any failure when setting up the basic context ( before the actual user's
process is launched ), nothing is captured by the NM. This makes it impossible to diagnose
the reason for the failure. 
> To reproduce, set an env var where the value contains characters that throw syntax errors
in bash. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message