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

ASF GitHub Bot commented on TWILL-63:
-------------------------------------

GitHub user gsps1 opened a pull request:

    https://github.com/apache/incubator-twill/pull/66

    TWILL-63, combining twill classes into a twill.jar and having other u…

    …ser classes into a program.jar, also caching the twill.jar in 
YarnTwillRunnerService and the content is reused across TwillApplications 
started by the runner

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gsps1/incubator-twill 
feature/twill-63-separating-twill-jars

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-twill/pull/66.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #66
    
----
commit 5d9bc9ff2df636f6881e4a091d0798cbca09254d
Author: shankar <[email protected]>
Date:   2015-10-07T21:59:35Z

    TWILL-63, combining twill classes into a twill.jar and having other user 
classes into a program.jar, also caching the twill.jar in 
YarnTwillRunnerService and the content is reused across TwillApplications 
started by the runner

----


> Speed up application launch time
> --------------------------------
>
>                 Key: TWILL-63
>                 URL: https://issues.apache.org/jira/browse/TWILL-63
>             Project: Apache Twill
>          Issue Type: Improvement
>          Components: yarn
>    Affects Versions: 0.2.0-incubating
>            Reporter: Terence Yim
>            Assignee: Shankar Selvam
>             Fix For: 0.7.0-incubating
>
>
> Currently when launching an application, two new jars are always created 
> locally, one for AM (appMaster.jar) and one for Container (container.jar) and 
> copied to HDFS before submitting the application. The jar files could 
> potentially be big and if it doesn't changed, it should require copying to 
> HDFS again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to