[jira] [Commented] (FLINK-4156) Job with -m yarn-cluster registers TaskManagers to another running Yarn session

["Aljoscha Krettek (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364110#comment-15364110 ] 

Aljoscha Krettek commented on FLINK-4156:
-----------------------------------------

This might be a show stopper for the 1.1 release. [~rmetzger], what do you think? Not being able to run multiple Flink-Yarn jobs in one Yarn cluster seems like a pretty big problem.

> 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
>            Reporter: Stefan Richter
>
> 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)