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

Peter Huang reassigned FLINK-39491:
-----------------------------------

    Assignee: Zhenqiu Huang  (was: Peter Huang)

> Move Create Job Event creation in Dispatcher 
> ---------------------------------------------
>
>                 Key: FLINK-39491
>                 URL: https://issues.apache.org/jira/browse/FLINK-39491
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / REST
>            Reporter: Zhenqiu Huang
>            Assignee: Zhenqiu Huang
>            Priority: Major
>              Labels: pull-request-available
>
> 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)

Reply via email to