[
https://issues.apache.org/jira/browse/TWILL-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867102#comment-15867102
]
Terence Yim commented on TWILL-217:
-----------------------------------
How about we start with building one extra jar, let's call it "amapp.jar", by
tracing dependency from the event handler and include that in the am classpath?
The changing of the ClassLoader model requires a much bigger effort and I don't
want it to block what you've been using twill for.
> AppMaster launcher should include eventHandler dependencies and nothing else
> from application
> ---------------------------------------------------------------------------------------------
>
> Key: TWILL-217
> URL: https://issues.apache.org/jira/browse/TWILL-217
> Project: Apache Twill
> Issue Type: Improvement
> Components: yarn
> Affects Versions: 0.9.0
> Reporter: Martin Serrano
> Assignee: Martin Serrano
>
> Currently the launcher for the appmaster includes the application.jar
> libraries. This is to support user code that adds an EventHandler. The
> application may have many dependencies and including them in the appmaster
> classpath can lead to otherwise inaddressable incompatibilities.
> In my case, something in my application's large dependency graph was
> interfering with the Kafka server operation. I was not able to determine
> what it was but tweaking the appmaster loader to not include my application
> jars fixed the issue.
> Instead the bundler that creates the twill.jar should include the
> EventHandler extension (if any) as an explicit dependency. In this way, only
> the jars needed to support the event handler will be on the twill classpath.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
