[GitHub] [flink] tillrohrmann opened a new pull request #9073: [FLINK-13187] Introduce ScheduleMode#LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST

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

tillrohrmann opened a new pull request #9073: [FLINK-13187] Introduce ScheduleMode#LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST
URL: https://github.com/apache/flink/pull/9073
 
 
   ## What is the purpose of the change
   
   This PR is based on #9058.
   
   The new ScheduleMode#LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST works similar to the
   old ScheduleMode#LAZY_FROM_SOURCES just with the difference that the slot requests
   call the SlotPool#requestNewAllocatedBatchSlot which requests batch slots. The
   idea of batch slots is that the requests won't time out as long as there is an
   allocated slot registered at the SlotPool which can fulfill the slot request
   (being equal or larger than the requested ResourceProfile).
   
   Hence, this ScheduleMode allows for batch job execution with fewer slots than requested.
   The user, however, has to make sure that every pipelined region of the submitted job requires
   only one slot to be executed!
   
   The different types of slot requests are encapsulated in the newly introduced
   SlotProviderStrategy. Depending on the ScheduleMode, the strategy will either call
   SlotProvider#allocateSlot or SlotProvider#allocateBatchSlot.
   
   cc @StephanEwen, @xintongsong 
   
   ## Verifying this change
   
   Added `LegacySchedulerBatchSchedulingTest`
   
   ## 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 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