Thesharing opened a new pull request #14864: URL: https://github.com/apache/flink/pull/14864
## What is the purpose of the change *This PR introduces several optimizations on scheduler performance for running large-scale jobs. The optimizations are involved with the following procedures:* * *Building topology when initializing ExecutionGraph* * *Building DefaultExecutionTopology* * *Initializing PipelinedRegionSchedulingStrategy* * *Scheduling downstream tasks when a task finishes* * *Calculating tasks to restart when a failover occurs* * *Releasing result partitions* *The main idea is to put all the vertices that consumed the same result partitions into one group, and put all the result partitions that have the same consumer vertices into one consumer group.* *For more details please check [FLINK-21110](https://issues.apache.org/jira/browse/FLINK-21110).* ## Brief change log - *Introduced EdgeManager, ConsumerVertexGroup and ConsumedPartitionGroup to store the topology in ExecutionGraph* - *Introduced several optimizations on the procedures we mentioned above based on EdgeManager* - *Removed ExecutionEdge and fixed related tests* ## Verifying this change *Since these optimizations do not change the original logic of the target procedures, we believe that this change is already covered by existing tests, such as ExecutionVertexDeploymentTest, DefaultExecutionTopologyTest, PipelinedRegionSchedulingStrategyTest, and etc.* ## 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, Kubernetes/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: us...@infra.apache.org
