[jira] [Commented] (FLINK-6031) Add parameter for per job yarn clusters to control whether the user code jar is included into the system classloader.

["Robert Metzger (JIRA)" <ji...@apache.org>]

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

Robert Metzger commented on FLINK-6031:
---------------------------------------

I responded on the BEAM issue.

Back to this one:
From the ML discussion, it seems that we need to have the following three options for controlling the user jar inclusion:
 - "user code first" or "user code last" in the classpath
 - no user code in the classpath
 

> 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)