You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Robert Metzger (Jira)" <ji...@apache.org> on 2021/03/19 18:51:00 UTC

[jira] [Created] (FLINK-21883) Introduce cooldown period into adaptive scheduler

Robert Metzger created FLINK-21883:
--------------------------------------

             Summary: Introduce cooldown period into adaptive scheduler
                 Key: FLINK-21883
                 URL: https://issues.apache.org/jira/browse/FLINK-21883
             Project: Flink
          Issue Type: Improvement
          Components: Runtime / Coordination
            Reporter: Robert Metzger
             Fix For: 1.14.0


This is a follow up to reactive mode, introduced in FLINK-10407.

Introduce a cooldown timeout, during which no further scaling actions are performed, after a scaling action.
Without such a cooldown timeout, it can happen with unfortunate timing, that we are rescaling the job very frequently, because TaskManagers are not all connecting at the same time.
With the current implementation (1.13), this only applies to scaling up, but this can also apply to scaling down with autoscaling support.

With this implemented, users can define a cooldown timeout of say 5 minutes: If taskmanagers are now slowly connecting one after another, we will only rescale every 5 minutes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)