[
https://issues.apache.org/jira/browse/FLINK-23697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17397104#comment-17397104
]
Till Rohrmann commented on FLINK-23697:
---------------------------------------
If you need Flink to start automatically new {{TaskExecutors}}, then you should
use Flink's active resource manager integration. You can either deploy on Yarn
or on Kubernetes and get the functionality you are looking for. Please also see
Flink's documentation about resource providers
([Yarn|https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/resource-providers/yarn/],
[Kubernetes|https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/].
> flink standalone Isolation is poor, why not do as spark does
> ------------------------------------------------------------
>
> Key: FLINK-23697
> URL: https://issues.apache.org/jira/browse/FLINK-23697
> Project: Flink
> Issue Type: Bug
> Reporter: jackylau
> Priority: Major
>
> flink standalone Isolation is poor, why not do as spark does.
> spark abstract cluster manager, executor just like flink taskmanager.
> spark worker(standalone) is process, and executor is as child process of
> worker.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
