flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maximilian Michels (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-4079) YARN properties file used for per-job cluster
Date Tue, 21 Jun 2016 12:23:57 GMT

     [ https://issues.apache.org/jira/browse/FLINK-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Maximilian Michels closed FLINK-4079.
    Resolution: Fixed

master: ec6d97528e8b21f191b7922e4810fd60804c8365
release-1.0: 3163638a61f49dd2df55467615096918bec3a890

Fix will be included in the 1.0.4 release.

> 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

View raw message