You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Sihua Zhou (JIRA)" <ji...@apache.org> on 2018/06/15 04:53:00 UTC
[jira] [Assigned] (FLINK-9455) Make SlotManager aware of multi slot
TaskManagers
[ https://issues.apache.org/jira/browse/FLINK-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sihua Zhou reassigned FLINK-9455:
---------------------------------
Assignee: Till Rohrmann (was: Sihua Zhou)
> 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: ResourceManager
> Affects Versions: 1.5.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Major
> Fix For: 1.6.0, 1.5.1
>
>
> 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)