hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-419) Add client side for Unmanaged-AMs
Date Wed, 06 May 2015 19:24:01 GMT

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

Vinod Kumar Vavilapalli updated YARN-419:
      Component/s: applications/unmanaged-AM-launcher
    Fix Version/s: 2.0.2-alpha

Setting the missing fix-version.

> Add client side for Unmanaged-AMs
> ---------------------------------
>                 Key: YARN-419
>                 URL: https://issues.apache.org/jira/browse/YARN-419
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: applications/unmanaged-AM-launcher
>    Affects Versions: 3.0.0
>            Reporter: Bikas Saha
>            Assignee: Bikas Saha
>             Fix For: 2.0.2-alpha
>         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 was sent by Atlassian JIRA

View raw message