[ 
https://issues.apache.org/jira/browse/FLINK-17017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhu Zhu closed FLINK-17017.
---------------------------
    Resolution: Fixed

Done via
7054f97350efec83e3bf8b10b9b2c44f1a149cf1
636e36cbd5bc2f45e0e502e0fec9d7723b06dd7a
ccc4d8e0d807ee2fff7d286cbecd904686aec44f
f6c275e26002abb42bfcc40ffbf6da54fbed4aa6
541f28fe4e0f90bde479fa457841e3cbc610f2ef
4c16a3468c65b876ac687a3805411aa3c7a9f295
044def9b50fe4249eaa3f1472981404425a11fd9
9aee0c0fb2121207bfdd7f824b61ff079b8ff884

> Implements bulk allocation for physical slots
> ---------------------------------------------
>
>                 Key: FLINK-17017
>                 URL: https://issues.apache.org/jira/browse/FLINK-17017
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>    Affects Versions: 1.11.0
>            Reporter: Zhu Zhu
>            Assignee: Zhu Zhu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.12.0
>
>
> SlotProvider should support bulk slot allocation so that we can check to see 
> if the resource requirements of a slot request bulk can be fulfilled at the 
> same time.
> The SlotProvider interface should be extended with an bulk slot allocation 
> method which accepts a bulk of slot requests as one of the parameters.
> {code:java}
> CompletableFuture<Collection<PhysicalSlotRequest.Result>> 
> allocatePhysicalSlots(
>   Collection<PhysicalSlotRequest> slotRequests,
>   Time timeout);
>  
> class PhysicalSlotRequest {
>   SlotRequestId slotRequestId;
>   SlotProfile slotProfile;
>   boolean slotWillBeOccupiedIndefinitely;
>   class Result {
>     SlotRequestId slotRequestId;
>     PhysicalSlot physicalSlot;
>   }
> }
> {code}
> More details see [FLIP-119#Bulk Slot 
> Allocation|https://cwiki.apache.org/confluence/display/FLINK/FLIP-119+Pipelined+Region+Scheduling#FLIP-119PipelinedRegionScheduling-BulkSlotAllocation]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to