[
https://issues.apache.org/jira/browse/FLINK-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15332002#comment-15332002
]
Ufuk Celebi commented on FLINK-4079:
------------------------------------
I understand where you are coming from, but it seems very weird to me that the
behaviour I describe can happen (where the first started long running Flink
session is actually still running, so the warning you mention would not be
shown).
I always had the mental model of "flink/bin bun -m yarn-cluster" starts a
cluster for this job only, which is not the case if we re-use the properties
file. I think that the properties file is mainly a concern for the long-lived
YARN session, where cluster start and job submission are not tied together.
> 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)
