[
https://issues.apache.org/jira/browse/FLINK-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maximilian Michels resolved FLINK-4156.
---------------------------------------
Resolution: Fixed
Fix Version/s: 1.1.0
Should be resolved with FLINK-4166.
> Job with -m yarn-cluster registers TaskManagers to another running Yarn
> session
> -------------------------------------------------------------------------------
>
> Key: FLINK-4156
> URL: https://issues.apache.org/jira/browse/FLINK-4156
> Project: Flink
> Issue Type: Bug
> Components: Distributed Coordination, YARN Client
> Reporter: Stefan Richter
> Fix For: 1.1.0
>
>
> When a job is started using cluster mode (-m yarn-cluster) and a Yarn session
> is running on the same cluster, the job accidentally registers it's worker
> tasks with the ongoing Yarn session. This happens because the same Zookeeper
> namespace is used.
> We should consider isolating Flink applications from another by using UUIDS,
> e.g. based on their application ids, in their Zookeeper paths.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
