Mailing-List: contact issues-help@flink.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.incubator.apache.org
Date: Tue, 11 Nov 2014 17:10:34 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@flink.incubator.apache.org
Message-ID: <JIRA.12725638.1404667944000.470014.1415725834180@Atlassian.JIRA>
In-Reply-To: <JIRA.12725638.1404667944000@Atlassian.JIRA>
References: <JIRA.12725638.1404667944000@Atlassian.JIRA>
 <JIRA.12725638.1404667944858@arcas>
Subject: [jira] [Commented] (FLINK-1003) Spread out scheduling strategy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Github user StephanEwen commented on the pull request:

    https://github.com/apache/incubator-flink/pull/60#issuecomment-62580255
  
    It is not included in FLINK-1030. This implementation is incompatible with the current scheduler implementation, unfortunately.


> 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)