[
https://issues.apache.org/jira/browse/FLINK-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907567#comment-15907567
]
Aljoscha Krettek edited comment on FLINK-6031 at 3/13/17 2:33 PM:
------------------------------------------------------------------
[~rmetzger] do you think this issue in the Beam Flink Runner could be cause by
this: BEAM-1640?
was (Author: aljoscha):
[~rmetzger] do you think this issue in the Beam Flink Runner could be cause by
this: https://issues.apache.org/jira/browse/BEAM-1640?
> Add parameter for per job yarn clusters to control whether the user code jar
> is included into the system classloader.
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-6031
> URL: https://issues.apache.org/jira/browse/FLINK-6031
> Project: Flink
> Issue Type: Bug
> Components: YARN
> Reporter: Robert Metzger
> Priority: Critical
>
> FLINK-4913 added the user jar into the system classloader, when starting a
> Flink per job YARN cluster.
> Some users were experiencing issues with the changed behavior.
> I suggest to introduce a new yarn specific configuration parameter (for the
> flink-conf.yaml file) to control if the user jar is added into system
> classloader.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
