hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Moved] (YARN-419) Add client side for Unmanaged-AMs (MAPREDUCE-4427)
Date Mon, 25 Feb 2013 06:52:18 GMT

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

Bikas Saha moved MAPREDUCE-4438 to YARN-419:

     Target Version/s:   (was: )
    Affects Version/s:     (was: 3.0.0)
                  Key: YARN-419  (was: MAPREDUCE-4438)
              Project: Hadoop YARN  (was: Hadoop Map/Reduce)
> Add client side for Unmanaged-AMs (MAPREDUCE-4427)
> --------------------------------------------------
>                 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
> 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

View raw message