[
https://issues.apache.org/jira/browse/FLINK-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16502064#comment-16502064
]
Sihua Zhou commented on FLINK-9455:
-----------------------------------
Hi [~till.rohrmann], I think this is a bit tricky than it looks like, I'd like
to have a brief discussion with you before jumping into the implementation
- Should we consider the situation that every request of the TM could with
different ResourceProfile? e.g. different cores and different TM memory.
Currently the TM's configuration is "immutable" for every cluster, but I can
see the trend that community may support request a user specific TM according
to their config.
- Should we hold the assumption that the ResourceProfile we requested from the
ResourceManager is definitely the same as the actual ResourceProfile we got
from the TM?
Or do you have any ideal on this ticket?
Thanks~
Sihua
> 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: Sihua Zhou
> 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)
