[
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551321#comment-16551321
]
Yinan Li edited comment on FLINK-4319 at 7/20/18 9:40 PM:
----------------------------------------------------------
Interested in FLIP-6 for Flink on Kubernetes. Wondering why the design for
deployment on Kubernetes is very different from those for the other cluster
managers. It looks like to me that users have to start a static number of
TaskManagers and the ResourceManager is not responsible for dynamically
spawning new TaskManagers on Kubernetes. If this is the case (correct me if I'm
wrong), what's the reason for this design?
P.S. I also work on the native Kubernetes scheduler backend for Spark.
was (Author: liyinan926):
Interested in bring FLIP-6 for Flink on Kubernetes. Wondering why the design
for deployment on Kubernetes is very different from the other cluster managers.
It looks like to me that users have to start a static number of TaskManagers
and the ResourceManager is not responsible for dynamically spawning new
TaskManagers on Kubernetes. If this is the case (correct me if I'm wrong),
what's the reason for this design?
P.S. I also work on the native Kubernetes scheduler backend for Spark.
> Rework Cluster Management (FLIP-6)
> ----------------------------------
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
> Issue Type: Improvement
> Components: Cluster Management
> Affects Versions: 1.1.0
> Reporter: Stephan Ewen
> Assignee: Till Rohrmann
> Priority: Major
> Labels: flip-6
> Fix For: 1.5.0
>
>
> This is the root issue to track progress of the rework of cluster management
> (FLIP-6)
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
