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 "Bikas Saha (JIRA)" <ji...@apache.org> on 2013/02/25 07:52:20 UTC

[jira] [Updated] (YARN-419) Add client side for Unmanaged-AMs

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

Bikas Saha updated YARN-419:
----------------------------

    Summary: Add client side for Unmanaged-AMs  (was: Add client side for Unmanaged-AMs (MAPREDUCE-4427))
    
> Add client side for Unmanaged-AMs
> ---------------------------------
>
>                 Key: YARN-419
>                 URL: https://issues.apache.org/jira/browse/YARN-419
>             Project: Hadoop YARN
>          Issue Type: Improvement
>    Affects Versions: 3.0.0
>            Reporter: Bikas Saha
>            Assignee: Bikas Saha
>         Attachments: MAPREDUCE-4438-1.patch, MAPREDUCE-4438-2.patch, MAPREDUCE-4438-3.patch
>
>
> MAPREDUCE-4427 added server side support for umanaged AM's. This tracks creating client side supporting pieces.
> The basic flow of the client is as follows
> 1) accepts a cmd line for the AM. Optional queue information etc.
> 2) negotiates an application id with the RM and submits the unmanaged AM.
> 3) waits for the AM to reach YarnApplicationState ACCEPTED
> 4) then launches the AM in a separate process via the cmd provided. It communicated application attempt id to the AM via env variable. Stdout and stderr is redirected to the clients streams respectively.
> 5) waits for the AM process to exit and RM app to complete.

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