You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2013/03/22 05:57:15 UTC

[jira] [Commented] (YARN-498) Unmanaged AM launcher does not set Container Id into env for an AM

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

Hitesh Shah commented on YARN-498:
----------------------------------

Found other issues in the unmanaged am launcher. 
  - More env vars are not set
  - It does not handle a failed AM properly - just hangs waiting for it to complete even after it has detected that the AM process has finished.
                
> Unmanaged AM launcher does not set Container Id into env for an AM
> ------------------------------------------------------------------
>
>                 Key: YARN-498
>                 URL: https://issues.apache.org/jira/browse/YARN-498
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Hitesh Shah
>            Assignee: Hitesh Shah
>         Attachments: YARN-498.wip.patch
>
>
> Currently, it only sets the app attempt id which is really not required as AMs are only expected to extract it from the container id.

--
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