You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2014/04/05 00:03:20 UTC
[jira] [Updated] (TEZ-684) Uber/Local modes for Tez
[ https://issues.apache.org/jira/browse/TEZ-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli updated TEZ-684:
----------------------------------------
Summary: Uber/Local modes for Tez (was: Uber-mode for Tez)
> 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: 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)