flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nico Kruber (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-12122) Spread out tasks evenly across all available registered TaskManagers
Date Tue, 21 May 2019 17:56:00 GMT

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

Nico Kruber commented on FLINK-12122:

I guess, as a workaround, you could have your memory intensive task run at the same parallelism
as your cluster (assuming you are using one cluster per job, this isn't such a bad thing after

> Spread out tasks evenly across all available registered TaskManagers
> --------------------------------------------------------------------
>                 Key: FLINK-12122
>                 URL: https://issues.apache.org/jira/browse/FLINK-12122
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>    Affects Versions: 1.6.4, 1.7.2, 1.8.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Major
>             Fix For: 1.7.3, 1.9.0, 1.8.1
>         Attachments: image-2019-05-21-12-28-29-538.png
> With Flip-6, we changed the default behaviour how slots are assigned to {{TaskManages}}.
Instead of evenly spreading it out over all registered {{TaskManagers}}, we randomly pick
slots from {{TaskManagers}} with a tendency to first fill up a TM before using another one.
This is a regression wrt the pre Flip-6 code.
> I suggest to change the behaviour so that we try to evenly distribute slots across all
available {{TaskManagers}} by considering how many of their slots are already allocated.

This message was sent by Atlassian JIRA

View raw message