You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yu Li (Jira)" <ji...@apache.org> on 2019/12/10 06:38:00 UTC

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

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

Yu Li updated FLINK-14510:
--------------------------
    Fix Version/s:     (was: 1.10.0)
                   1.11.0

Change fix version to 1.11.0 since we already reached feature freeze for 1.10.0

> 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
>             Fix For: 1.11.0
>
>
> 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)