You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Sergey Nuyanzin (Jira)" <ji...@apache.org> on 2026/04/22 12:02:00 UTC

[jira] [Updated] (FLINK-39491) Move Create Job Event creation in Dispacher

     [ https://issues.apache.org/jira/browse/FLINK-39491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Nuyanzin updated FLINK-39491:
------------------------------------
    Fix Version/s:     (was: 2.1.2)

> Move Create Job Event creation in Dispacher 
> --------------------------------------------
>
>                 Key: FLINK-39491
>                 URL: https://issues.apache.org/jira/browse/FLINK-39491
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / REST
>            Reporter: Zhenqiu Huang
>            Priority: Major
>
> Currently, the job creation event happens in client side, and any follow up status change events propagation happen in DefaultExecutionGraph. In this case, there are two instances of the same job listener created. We probably may consider moving the job creation event to dispatcher. With the change, a single job listener instance for each type in JVM needs to be created.  Then, states within the instance will be shared within the whole job lifecycle.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)