[
https://issues.apache.org/jira/browse/FLINK-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015505#comment-16015505
]
ASF GitHub Bot commented on FLINK-6031:
---------------------------------------
Github user rmetzger commented on a diff in the pull request:
https://github.com/apache/flink/pull/3931#discussion_r117204403
--- Diff: docs/setup/yarn_setup.md ---
@@ -245,6 +245,18 @@ Note: You can use a different configuration directory
per job by setting the env
Note: It is possible to combine `-m yarn-cluster` with a detached YARN
submission (`-yd`) to "fire and forget" a Flink job to the YARN cluster. In
this case, your application will not get any accumulator results or exceptions
from the ExecutionEnvironment.execute() call!
+### User jars & Classpath
+
+By default Flink will include the user jars into the system classpath when
running a single job. This behavior can be controlled with the
`yarn.per-job-cluster.include-job-jar` parameter.
--- End diff --
The configuration parameter is actually called
`yarn.per-job-cluster.include-user-jar`.
> 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
> Assignee: Chesnay Schepler
> 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)
