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

Posted to issues@tez.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2014/07/30 07:16:38 UTC

[jira] [Resolved] (TEZ-707) Create LocalContainerLauncher

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

Siddharth Seth resolved TEZ-707.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 0.5.0

Committed to master.

> Create LocalContainerLauncher
> -----------------------------
>
>                 Key: TEZ-707
>                 URL: https://issues.apache.org/jira/browse/TEZ-707
>             Project: Apache Tez
>          Issue Type: Sub-task
>    Affects Versions: 0.3.0
>            Reporter: Chen He
>            Assignee: Chen He
>            Priority: Blocker
>             Fix For: 0.5.0
>
>         Attachments: TEZ-707-2014-7015.patch, TEZ-707-2014-7015.patch.review, TEZ-707-v10.patch, TEZ-707-v3.patch, TEZ-707-v4.patch, TEZ-707.patch, TEZ-707.patch, TEZ-707.patch, Tez-707.patch.v2, tez-707.patch
>
>
> Create LocalContainerLauncher and make it work for a single stage DAG. The TaskSchedulerEventHandler still asks RM for new container but LocalContainerLauncher will run TezTask in form of thread instead of using this container from yarn. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)