[
https://issues.apache.org/jira/browse/FLINK-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maximilian Michels resolved FLINK-4079.
---------------------------------------
Resolution: Not A Problem
This is a feature :) The Yarn properties file is supposed to be picked up. We
can't break this behavior because users rely on it.
My changes will give an appropriate error message if the properties file
configuration doesn't correspond to a running application in the Yarn cluster.
> 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
> Affects Versions: 1.0.3
> Reporter: Ufuk Celebi
> Fix For: 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)
