flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-6031) Add parameter for per job yarn clusters to control whether the user code jar is included into the system classloader.
Date Thu, 18 May 2017 09:35:04 GMT

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

ASF GitHub Bot commented on FLINK-6031:

Github user rmetzger commented on a diff in the pull request:

    --- 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`
    +When setting this to `DISABLED` Flink will include the jar in the user classpath instead.
    +The user-jars position in the class path can be controlled by setting the parameter to
one of the following:
    +- `ORDER`: (default) Adds the jar to the system class path based on the lexicographic
    +- `FIRST`: Adds the jar to the beginning of the system class path.
    +- `LAST`: Adds the jar to the end of the system class path.
    --- End diff --
    Ideally, you put the configuration property also into the  `setup/config.md` page, where
all config options are listed.

> 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

View raw message