[jira] [Closed] (FLINK-9455) Make SlotManager aware of multi slot TaskManagers

["Till Rohrmann (JIRA)" <ji...@apache.org>]

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

Till Rohrmann closed FLINK-9455.
--------------------------------
      Resolution: Fixed
    Release Note: Flink now properly supports TaskExecutors with multiple slots. Consequently, TaskExecutors can now be started with an arbitrary number of slots and it is no longer recommended to start them with a single slot. 

Fixed via 771277b42427d55b52a28d5893c71c3b8de97807

> Make SlotManager aware of multi slot TaskManagers
> -------------------------------------------------
>
>                 Key: FLINK-9455
>                 URL: https://issues.apache.org/jira/browse/FLINK-9455
>             Project: Flink
>          Issue Type: Improvement
>          Components: Distributed Coordination, ResourceManager
>    Affects Versions: 1.5.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.7.0
>
>
> The {{SlotManager}} responsible for managing all available slots of a Flink cluster can request to start new {{TaskManagers}} if it cannot fulfill a slot request. The started {{TaskManager}} can be started with multiple slots configured but currently, the {{SlotManager}} thinks that it will be started with a single slot. As a consequence, it might issue multiple requests to start new TaskManagers even though a single one would be sufficient to fulfill all pending slot requests.
> In order to avoid requesting unnecessary resources which are freed after the idle timeout, I suggest to make the {{SlotManager}} aware of how many slots a {{TaskManager}} is started with. That way the SlotManager only needs to request a new {{TaskManager}} if all of the previously started slots (potentially not yet registered and, thus, future slots) are being assigned to slot requests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)