You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "David Morávek (Jira)" <ji...@apache.org> on 2022/12/12 09:03:00 UTC
[jira] [Commented] (FLINK-25334) Manage and share gateways of taskmanagers between jobs in session cluster
[ https://issues.apache.org/jira/browse/FLINK-25334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645982#comment-17645982 ]
David Morávek commented on FLINK-25334:
---------------------------------------
Can you please provide some details on how you intend to implement this, w.r.t. supporting the split of JM components into separate processes?
> Manage and share gateways of taskmanagers between jobs in session cluster
> -------------------------------------------------------------------------
>
> Key: FLINK-25334
> URL: https://issues.apache.org/jira/browse/FLINK-25334
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.14.0, 1.12.4, 1.13.3
> Reporter: Shammon
> Priority: Major
>
> Flink session cluster launches a certain number of taskmanagers and they won't exit during the cluster running. When a job is submitted to the cluster, taskmanagers will offer slots to `JobMaster` with location info. Then `JobMaster` will get `InetAddress` from the location and connect the taskmanager. This cause some performance loss and it isn't necessary in session cluster.
> It's better to manager the gateways of taskmanagers in JM and share them between jobs. When a taskmanager's gateway is exist and valid, the `JobMaster` can use it directly instead of creating a new one.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)