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

["Siddharth Seth (JIRA)" <ji...@apache.org>]

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

Siddharth Seth commented on TEZ-684:
------------------------------------

Folks, I'm planning to close this out since LocalMode exists now. The pending issues can move under a sub-jira. Will do this later today unless there are objections.

> 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-2014-7-21.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, 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.3.4#6332)