[jira] [Commented] (FLINK-1003) Spread out scheduling strategy

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362238#comment-15362238 ] 

ASF GitHub Bot commented on FLINK-1003:
---------------------------------------

Github user StephanEwen commented on the issue:

    https://github.com/apache/flink/pull/2129
  
    I think the implementation looks good.
    
    The big question for this is actually more whether this interplays nicely with other changes around dynamic scaling. Once we have that part figured out and we see it works together well, this change is probably good.
    
    In order to figure that out, let's try and actually collect and write up the designs for how the system will evolve with respect to dynamic scaling.


> Spread out scheduling strategy
> ------------------------------
>
>                 Key: FLINK-1003
>                 URL: https://issues.apache.org/jira/browse/FLINK-1003
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: Till Rohrmann
>            Assignee: Gyula Fora
>
> Currently the Flink scheduler tries to fill one instance completely before the tasks are deployed to another instance. This is a good behaviour in multi-user and multi-job scenarios but it wastes resources if one wants to use the complete cluster. Therefore, another scheduling strategy where the load among the different instances is kept balanced might be useful. This spread out strategy will deploy the tasks such that the overall work is equally distributed.



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