[
https://issues.apache.org/jira/browse/FLINK-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15671478#comment-15671478
]
ASF GitHub Bot commented on FLINK-4913:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2795
I also was very torn when it came to this change.
In the end, I lean towards keeping user behavior in 1.1.4 consistent. The
fix is in 1.2, which is not too far away, and there it is great!
> Per-job Yarn clusters: include user jar in system class loader
> ---------------------------------------------------------------
>
> Key: FLINK-4913
> URL: https://issues.apache.org/jira/browse/FLINK-4913
> Project: Flink
> Issue Type: Improvement
> Components: Client, YARN Client
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Fix For: 1.2.0, 1.1.4
>
>
> Including the jar directly in the system classloader avoids loading it for
> every instantiation of the ExecutionGraph and every Task execution. Note,
> this is only possible for per-job clusters (i.e. Yarn/Mesos).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
