You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2016/09/04 21:13:20 UTC

[jira] [Closed] (FLINK-4459) Introduce SlotProvider for Scheduler

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

Stephan Ewen closed FLINK-4459.
-------------------------------

> Introduce SlotProvider for Scheduler
> ------------------------------------
>
>                 Key: FLINK-4459
>                 URL: https://issues.apache.org/jira/browse/FLINK-4459
>             Project: Flink
>          Issue Type: Improvement
>          Components: Scheduler
>            Reporter: Till Rohrmann
>            Assignee: Kurt Young
>             Fix For: 1.2.0
>
>
> Currently the {{Scheduler}} maintains a queue of available instances which it scans if it needs a new slot. If it finds a suitable instance (having free slots available) it will allocate a slot from it. 
> This slot allocation logic can be factored out and be made available via a {{SlotProvider}} interface. The {{SlotProvider}} has methods to allocate a slot given a set of location preferences. Slots should be returned as {{Futures}}, because in the future the slot allocation might happen asynchronously (Flip-6). 
> In the first version, the {{SlotProvider}} implementation will simply encapsulate the existing slot allocation logic extracted from the {{Scheduler}}. When a slot is requested it will return a completed or failed future since the allocation happens synchronously.
> The refactoring will have the advantage to simplify the {{Scheduler}} class and to pave the way for upcoming refactorings (Flip-6).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)