zhuzhurk opened a new pull request #8851: [FLINK-12876] [runtime] Add an 
adapter of region failover NG for legacy scheduler
URL: https://github.com/apache/flink/pull/8851
 
 
   
   ## What is the purpose of the change
   
   *This PR adds an adapter to adapt flip1.RestartPipelinedRegionStrategy for 
legacy scheduler, so that the legacy scheduler can support fine grained 
recovery.*
   
   
   ## Brief change log
   
     - *An adapter of flip1.RestartPipelinedRegionStrategy. It implements 
interfaces of the old FailoverStrategy to support the legacy scheduler.*
     - *A vertex versioner from Gary to maintain vertex versions. This helps to 
deal with concurrent region failovers.*
    - *A scheduling util that implements similar scheduling logic to 
ExecutionGraph for failover purposes.*
   
   
   ## Verifying this change
   
   *(Please pick either of the following options)*
   
   This change added tests and can be verified as follows:
   
     - *Tests for strategy loading and building*
     - *Tests for basic failover handling*
     - *Tests for concurrent failovers handling*
   
   ## 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 yet)
   

----------------------------------------------------------------
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

Reply via email to