[
https://issues.apache.org/jira/browse/FLINK-35417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
melin updated FLINK-35417:
--------------------------
Description:
flink is widely used in data integration scenarios, where a single concurrency
is not high, and in many cases a single concurrency can run a task. Consider
the high availability, application mode, and large number of JobManger nodes
that cost a lot of resources. If the Session mode is used, the stability is not
high.
In application mode, JobManager and TaskManager can be run together to achieve
reliability and save resources.
was:Spark is used in data integration scenarios (such as reading data from
mysql and writing data to other data sources), and in many cases can run tasks
in a single concurrency. The Driver and Executor consume resources separately.
If Driver and Executor support merging, especially when running on the cloud.
Can save calculation cost.
> JobManager and TaskManager support merging and run in a single process
> ----------------------------------------------------------------------
>
> Key: FLINK-35417
> URL: https://issues.apache.org/jira/browse/FLINK-35417
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: melin
> Assignee: Jeyhun Karimov
> Priority: Major
>
> flink is widely used in data integration scenarios, where a single
> concurrency is not high, and in many cases a single concurrency can run a
> task. Consider the high availability, application mode, and large number of
> JobManger nodes that cost a lot of resources. If the Session mode is used,
> the stability is not high.
> In application mode, JobManager and TaskManager can be run together to
> achieve reliability and save resources.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
