flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-1003) Spread out scheduling strategy
Date Mon, 01 Sep 2014 16:08:21 GMT

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

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

Github user StephanEwen commented on the pull request:

    https://github.com/apache/incubator-flink/pull/60#issuecomment-54075422
  
    This is a very nice idea. I'll try and incorporate it into the following effort: https://issues.apache.org/jira/browse/FLINK-1030


> 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: Till Rohrmann
>
> 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)

Mime
View raw message