[jira] [Updated] (FLINK-14510) Remove the lazy vertex attaching mechanism from ExecutionGraph

["Flink Jira Bot (Jira)" <ji...@apache.org>]

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

Flink Jira Bot updated FLINK-14510:
-----------------------------------
    Labels: auto-unassigned stale-major  (was: auto-unassigned)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> Remove the lazy vertex attaching mechanism from ExecutionGraph
> --------------------------------------------------------------
>
>                 Key: FLINK-14510
>                 URL: https://issues.apache.org/jira/browse/FLINK-14510
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>    Affects Versions: 1.10.0
>            Reporter: Zhu Zhu
>            Priority: Major
>              Labels: auto-unassigned, stale-major
>
> Currently in production, the vertex attaching is only invoked right after the ExecutionGraph is created in ExecutionGraphBuilder. That means lazy attaching is not necessary at the moment. It however adds extra complexity to ExecutionGraph, since we need to assume that the vertices may be not initialized or even get changed.
> Moreover, attaching vertices after a job starts scheduling is an undefined behavior which would not work properly.
> I'd propose to remove the lazy attaching mechanism, and do vertices building and related components initialization in ExecutionGraph constructor. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)