[jira] [Comment Edited] (TEZ-707) Get a single vertex DAG work in Uber-mode

["Chen He (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TEZ-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920909#comment-13920909 ] 

Chen He edited comment on TEZ-707 at 3/5/14 7:02 PM:
-----------------------------------------------------

Hi [~sseth]

Back to your first suggestion. The YTDC is a class without constructor and only has main method. To use it without creating new JVM, I have to modify its code. My plan is to modify the LCL and let it control the parallelism of running tasks from same vertex. The YTDC will extend Thread and have a run method as stub for LCL to use it directly. I don't want to waste time from both side. Do you have any suggestion for this plan? Thank you in advance.


was (Author: airbots):
Hi [~sseth]

Back to your first suggestion. The YTDC is a class without constructor and only has main method. To use it without creating new JVM, I have to modify its own code. My plan is to modify the LCL and let it control the parallelism of running tasks from same vertex. The YTDC will extend Thread and have a run method as stub for LCL to use it directly. I don't want to waste time from both side. Do you have any suggestion for this plan? Thank you in advance.

> 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.2#6252)