rkhachatryan opened a new pull request, #21981:
URL: https://github.com/apache/flink/pull/21981

   ## What is the purpose of the change
   
   Adjust slot assignment by Adaptive Scheduler
   to try to re-use previous allocations
   so that TMs can use Local Recovery.
   
   Contributed mostly by @dmvk.
   The main defferences from the original contribution:
   1. Previous `ExecutionGraph` is passed from the previous state explicitly 
(currently, `WaitingForResources` stage, which triggers the computation, 
doesn't have the graph)
   2. In `SlotAssigner`, the split into two methods is removed mostly for 
consistency (two methods mostly duplicated each other). That results in higher 
asymptotical complexity of `StateLocalitySlotAssigner` (`O(mnlog*mnlog)` vs 
`O(mnlog`)
   3. DoP is computed according to FLINK-30895
   
   ## Brief change log
   
    - Support LocalRecovery by AdaptiveScheduler
    - Add previous ExecutionGraph to WaitingForResources AdaptiveScheduler state
    - Make LocalRecoveryITCase fail when allocations don't match
   
   ## Verifying this change
   
   - Adjusted `LocalRecoveryITCase`
   - Added `SlotSharingSlotAllocatorTest.testStickyAllocation`
   
   ## 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, 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.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to