zhuzhurk opened a new pull request #9165: [FLINK-13055] [runtime] Leverage JM tracked partitions to find out unavailable partitions in … URL: https://github.com/apache/flink/pull/9165 …time ## What is the purpose of the change *In current region failover process, most of the input result partition states are unknown. Even though the failure cause is a PartitionException, only one unhealthy partition can be identified.* *The may lead to multiple unsuccessful failovers before all the unhealthy but needed partitions are identified and their producers are involved in the failover as well. (unsuccessful failover here means the recovered tasks get failed again soon due to some missing input partitions.)* *This PR leverages JM side tracked partition states to help the region failover to identify unhealthy(missing) partitions earlier, thus to improve the failover experience.* ## Brief change log - *Implemented ExecutionGraphResultPartitionAvailabilityChecker* - *Let ExecutionGraph build its ExecutionGraphResultPartitionAvailabilityChecker and use it to generate region failover strategy* - *Enabled PartitionTracker to support querying whether a given partition is tracked* ## Verifying this change - *Added UT for ExecutionGraphResultPartitionAvailabilityChecker* ## 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
