zhuzhurk opened a new pull request #9954: [FLINK-14330][runtime] Keep only one execution topology in scheduler URL: https://github.com/apache/flink/pull/9954 ## What is the purpose of the change Currently there are 3 failover topology instances created, 2 permanently kept in JM. 2 scheduling topology instances created permanently kept in JM. It a waste of computation to build the topologies and memory to keep these topologies. Which may be a significant issue when the job scale is large. With FLINK-14450 and FLINK-14451, the SchedulingTopology and FailoverTopology are able to share one default implementation. It enables us to change the scheduler to create and keep only one such an execution topology instance to reduce the cost to build and host execution topologies. This PR is to change the scheduler to create and keep only one execution topology instance. ## Brief change log - *hotfix: Rename ExecutionGraphToSchedulingTopologyAdapter to DefaultExecutionTopology* - *Remove duplicated execution topology creation and keep the only created one* ## Verifying this change This change is a trivial rework / code cleanup without any test coverage. This change is already covered by existing tests of scheduling and failover*. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (yes / **no**) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**) - The serializers: (yes / **no** / don't know) - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (**yes** / no / don't know) - The S3 file system connector: (yes / **no** / don't know) ## Documentation - Does this pull request introduce a new feature? (yes / **no**) - If yes, how is the feature documented? (**not applicable** / docs / JavaDocs / not documented)
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
