[jira] [Comment Edited] (TEZ-684) Uber/Local modes for Tez

["Chen He (JIRA)" <ji...@apache.org>]

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

Chen He edited comment on TEZ-684 at 7/14/14 10:33 PM:
-------------------------------------------------------

latest update that can support pig single DAG. Need pig-4008 for latest pig code


was (Author: airbots):
latest update that can support pig single DAG and has TestTezLocalJob unit test code. Need pig-4008 for latest pig code

> Uber/Local modes for Tez
> ------------------------
>
>                 Key: TEZ-684
>                 URL: https://issues.apache.org/jira/browse/TEZ-684
>             Project: Apache Tez
>          Issue Type: New Feature
>            Reporter: Chen He
>            Assignee: Chen He
>         Attachments: TEZ-684.patch, TEZ-684.patch, TEZ-684.patch, TEZ-684.patch, TEZ-684.patch, TEZ-684.patch, TEZ-684.patch, TEZ-684.patch, TEZ-684.patch, TEZ-684.patch, TEZ-684.patch, TEZ-684.patch, TezUberModeDesignDraft.png
>
>
> Similarly to MapReduce Uber-mode in Yarn, we plan to create the Uber-mode for Tez. It runs all tasks in local in one process.
> Our target is to start DAGAppMaster in local JVM and let it run all tasks in one process. 
> Here is my design: 
> Once user submits a DAG, Tez starts a instance of DAGAppMaster. This DAGAppMaster will check TezConfiguration before instantiate ContainerLauncher. If "is_Uber" is true, DAGAppMaster creates a LocalContainerLauncher. LocalTaskScheduler and LocalTaskSchedulerEventHandler will call LocalContainerLauncher to run all tasks one by one in a single JVM. Communications between ResourceManager and local classes (DAGAppMaster, LocalContainerLauncher, LocalTaskScheduler, and LocalTaskSchedulerEventHandler) are muted.



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