[GitHub] [flink] zhuzhurk opened a new pull request #8316: [FLINK-12369] [coordination] Implement a region failover strategy regarding the next version FailoverStrategy interfaces

[GitBox <gi...@apache.org>]

zhuzhurk opened a new pull request #8316: [FLINK-12369] [coordination] Implement a region failover strategy regarding the next version FailoverStrategy interfaces
URL: https://github.com/apache/flink/pull/8316
 
 
   ## What is the purpose of the change
   
   *This pull request implements a region failover strategy regarding the next version FailoverStrategy interfaces. The new FailoverStrategy is only responsible for returning vertices that need to be restarted. This rewrite is necessary to support the backtracking of missing result partitions in region failover. *
   
   
   ## Brief change log
   
     - *Add new FailoverStrategy interface*
     - *Add a FailoverTopology and related component interfaces to provide necessary topology info to FailoverStrategy*
     - *Add a new version RestartPipelinedRegionStrategy, it is a re-write of existing rg.apache.flink.runtime.executiongraph.failover.RestartPipelinedRegionStrategy, including the faiover handling and region building.*
     - *Add region building tests for the new strategy, which is a re-write of existing region building tests.*
   
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
     - *region building tests are added for the new strategy. It is a re-write of existing region building tests*
     - *test cases are added to verify the getTasksNeedingRestart logic*
     - *region building perf test is conducted, for a 10000x6000 scale job with All-to-All edges, it costs ~4s to build all the regions*
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): (no)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (no)
     - If yes, how is the feature documented? (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:
users@infra.apache.org


With regards,
Apache Git Services