tillrohrmann opened a new pull request #6734: [FLINK-9455][RM] Add support for 
multi task slot TaskExecutors
URL: https://github.com/apache/flink/pull/6734
 
 
   ## What is the purpose of the change
   
   This PR adds support for multi task slot TaskExecutors to Flink. Before it 
was recommended to start a Flink cluster with single slot `TaskExecutors`. Now 
also multi slot `TaskExecutors` can be configured and Flink won't allocate 
resources over-excessively.
   
   ## Brief change log
   
   - Extend `ResourceActions#allocateResource` to return 
`Collection<ResourceProfile>` indicating the set of slots to expect
   - Store expected slots as `PendingTaskManagerSlot`
   - Use `PendingTaskManagerSlot` to fulfill `PendingSlotRequest`
   - Only ask for new resources if there are no more `TaskManagerSlots` and 
`PendingTaskManagerSlots`
   
   ## Verifying this change
   
   - Added `SlotManagerTest#`: `testRequestNewResources`, 
`testFailingAllocationReturnsPendingTaskManagerSlot`, 
`testPendingTaskManagerSlotCompletion`, `testRegistrationOfDifferentSlot`, 
`testOnlyFreeSlotsCanFulfillPendingTaskManagerSlot`, 
   
   ## 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 applicable)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


With regards,
Apache Git Services

Reply via email to