[
https://issues.apache.org/jira/browse/TEZ-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096467#comment-14096467
]
Siddharth Seth edited comment on TEZ-684 at 8/14/14 2:28 AM:
-------------------------------------------------------------
LocalResources are not handled in local mode. I'm not sure if there's a jira
for this or not. It's a fairly complicated, and far-reaching change to get
something like this to work. Will require the concept of a working directory -
which would then have to be explicitly used.
In most cases, this isn't a problem since required libraries are already part
of the client / AM. For custom resources though - this is problematic. That's
the main reason SplitsOnClient_DistCache does not function.
was (Author: sseth):
LocalResources are not handled in local mode. I'm not sure if there's a jira
for this or not. It's a fairly complicated, and far-reaching change to get
something like this to work. Will require the concept of a working directory -
which would then have to be explicitly 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)
