[
https://issues.apache.org/jira/browse/FLINK-35417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848514#comment-17848514
]
Xintong Song commented on FLINK-35417:
--------------------------------------
Hi [~melin],
Please help me understand. Are you willing to make a contribution on the
proposed feature? Or are you only expressing a demand but has no intention to
work on it?
If you'd like to contribute, I agree with [~martijnvisser] that this is a bit
too big for a Jira ticket. Please propose this on the mailing list. My gut
feeling this would introduce a new deployment mode, as well as public interface
changes, which means it needs to go through a FLIP process.
If you're only making a demand, then I think this is a valid demand. We have
similar observations in our production, and I have even thought about similar
ideas. Unfortunately, I haven't yet find enough time and resources to work on
it.
> 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: API / Core
> Reporter: melin
> 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)
