[
https://issues.apache.org/jira/browse/TEZ-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14083337#comment-14083337
]
Siddharth Seth commented on TEZ-684:
------------------------------------
Once TEZ-1343 goes in (it's almost ready - patch needs some changes, almost all
of which are non functional) - I think local mode is good to go. Pig has
already started some testing with it. If folks are OK with it, I'll move the
pending jiras into a "Local Mode enhancement" sub-jira. The critical bit
rightnow will is documentation and how to use this - which I'll leave as a
sub-task here.
[~airbots], [~jeagles], [~pramachandran] - thanks for all the patches and
iterations!
Current usage requirements:
1. Clients need to set "tez.local.mode" to true when creating a TezClient
instance. (For the examples this can be done via -Dtez.local.mode=true)
2. fs.defaultFS must be set to "file:///"
2.1 If running examples - this must be set in tez-site.xml (so that it's
picked up by the client, as well as the conf instances used to configure the
Inputs / Outputs).
2.2 If using programatically (without a tez-site.xml present). All
configuration instances used (to crate the client / configure Inputs / Outputs)
- must have this property set.
3. tez.staging-dir must be set (either programatically or via tez-site.xml).
Until TEZ-1337 goes in - the staging-dir for the job is effectively the root of
the filesystem (and where inputs are read from / written to if relative paths
are used).
> 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.2#6252)
