[
https://issues.apache.org/jira/browse/FLINK-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341409#comment-15341409
]
ASF GitHub Bot commented on FLINK-4079:
---------------------------------------
GitHub user mxm opened a pull request:
https://github.com/apache/flink/pull/2140
[FLINK-4079] do not load Yarn properties file for per-job Yarn clusters
This is a backported fix for the release-1.0 branch to skip loading of the
Yarn properties file for per-job Yarn clusters.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mxm/flink release-1.0
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2140.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2140
----
commit 81823b99379e223ef5d6020dedc540518c156049
Author: Maximilian Michels <m...@apache.org>
Date: 2016-06-21T09:03:25Z
[FLINK-4079] do not load Yarn properties file for per-job Yarn clusters
----
> YARN properties file used for per-job cluster
> ---------------------------------------------
>
> Key: FLINK-4079
> URL: https://issues.apache.org/jira/browse/FLINK-4079
> Project: Flink
> Issue Type: Bug
> Components: Client
> Affects Versions: 1.0.3
> Reporter: Ufuk Celebi
> Assignee: Maximilian Michels
> Fix For: 1.1.0, 1.0.4
>
>
> YARN per job clusters (flink run -m yarn-cluster) rely on the hidden YARN
> properties file, which defines the container configuration. This can lead to
> unexpected behaviour, because the per-job-cluster configuration is merged
> with the YARN properties file (or used as only configuration source).
> A user ran into this as follows:
> - Create a long-lived YARN session with HA (creates a hidden YARN properties
> file)
> - Submits standalone batch jobs with a per job cluster (flink run -m
> yarn-cluster). The batch jobs get submitted to the long lived HA cluster,
> because of the properties file.
> [~mxm] Am I correct in assuming that this is only relevant for the 1.0 branch
> and will be fixed with the client refactoring you are working on?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
