[
https://issues.apache.org/jira/browse/FLINK-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053628#comment-14053628
]
ASF GitHub Bot commented on FLINK-1003:
---------------------------------------
Github user StephanEwen commented on a diff in the pull request:
https://github.com/apache/incubator-flink/pull/60#discussion_r14594319
--- Diff:
stratosphere-tests/src/test/java/eu/stratosphere/test/exampleJavaPrograms/WordCountITCase.java
---
@@ -26,7 +27,8 @@
public WordCountITCase(){
setDegreeOfParallelism(4);
setNumTaskTracker(2);
- setTaskManagerNumSlots(2);
+ setTaskManagerNumSlots(4);
--- End diff --
With a dop of 4, it should be enough to have 2 taskmanagers with 2 slots.
Or is the number of slots the total number?
> 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.2#6252)
