[
https://issues.apache.org/jira/browse/TEZ-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908425#comment-13908425
]
Chen He edited comment on TEZ-707 at 2/21/14 3:19 PM:
------------------------------------------------------
Hi [~sseth], Thank you for your comments.
I can answer your question one by one:
1) Right now, the map-only job can not run more than one map task at the same
time. My first target is to come up with a simple workable version for user to
test their tez job;
2) Our final target is to get ride of RPC communication, right? Since these
processes will be in same JVM, we may not need to force the
localcontainerlauncher to use PRC;
3) I created TEZ-870 to solve this problem;
4) Vertex level uber/local mode checking will be done in TEZ-869;
was (Author: airbots):
Hi [~sseth], Thank you for your comments.
I can answer your question one by one:
1) Right now, the map-only job can not run more than one map task at the same
time. My first target is to come up with a simple workable version for user to
test their tez job;
2) Our final target is to get ride of RPC communication, right? Since these
processes will be in same JVM, we may not need to force the
localcontainerlauncher to use PRC;
3) I created Tez-870 to solve this problem;
4) Vertex level uber/local mode checking will be done in TEZ-869;
> Get a single vertex DAG work in Uber-mode
> ------------------------------------------
>
> Key: TEZ-707
> URL: https://issues.apache.org/jira/browse/TEZ-707
> Project: Apache Tez
> Issue Type: Sub-task
> Affects Versions: 0.3.0
> Reporter: Chen He
> Assignee: Chen He
> Attachments: tez-707.patch
>
>
> Create LocalContainerLauncher and make it work for a single stage DAG. The
> TaskSchedulerEventHandler still asks RM for new container but
> LocalContainerLauncher will run TezTask in form of thread instead of using
> this container from yarn.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
