[
https://issues.apache.org/jira/browse/FLINK-32255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729721#comment-17729721
]
Gyula Fora commented on FLINK-32255:
------------------------------------
This feature is mostly relevant for the native integration (because in
standalone mode the TM number is "fixed" anyways). This also means that it
would have to be implemented on the Flink side. I think we could change the
semantics of this config to start an empty TM always.
I would at least start a short discussion in the dev mailing list to see what
others think. Can you do that?
> Pre-deployed idle Task Managers
> -------------------------------
>
> Key: FLINK-32255
> URL: https://issues.apache.org/jira/browse/FLINK-32255
> Project: Flink
> Issue Type: New Feature
> Components: Kubernetes Operator
> Reporter: Christophe Bornet
> Priority: Major
>
> In the kubernetes operator, it would be nice to have the possibility to
> define a number of pre-deployed spare Task Managers. The operator would
> ensure that there are always a number of ready-to-be-used TMs that can accept
> new incoming jobs.
> The goal would be to reduce the startup time of jobs, especially in the
> session cluster mode.
> See for inspiration
> [https://www.decodable.co/blog/flink-deployments-at-decodable] -> Custom
> Flink Session Clusters for Preview Jobs: "To further reduce the preview
> response time, we also modified Flink to pre-deploy some idle TaskManagers.
> When a TaskManager is used, a new TaskManager is immediately created so there
> is always a pool of idle TaskManagers."
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
