[
https://issues.apache.org/jira/browse/TEZ-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14251089#comment-14251089
]
Bikas Saha commented on TEZ-684:
--------------------------------
Chen, I dont think that was the intention when removing assignee on this jira.
While the code is not owned by anyone, the contributions made by someone are
credited when the patches contributed by them are committed to the code base.
That credit history is recorded in the git or svn commit history for the
project. Being a jira assignee for that patch's jira is less of a record. E.g.
when multiple people help in creating the patch for a jira then the commit log
for that patch credits all of them, even though the jira is assigned to only 1
of them.
AFAIK, there is no convention regarding umbrella jiras. Some people assign
umbrella jiras because they are driving most of the sub-tasks while some prefer
to leave them unassigned since the actual work is being done in the sub-task
jiras. As is clearly obvious from the sub-tasks of this jira and the project
commit log, you (and others) have made many contributions to the project (and
in local mode code).
I hope this clarifies.
> 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
> Fix For: 0.5.0
>
> 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)
