[
https://issues.apache.org/jira/browse/FLINK-21883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779741#comment-17779741
]
Rui Fan commented on FLINK-21883:
---------------------------------
Thanks [~echauchot] for your effort!:)
Merged to master (1.19) via 3ff225c5f993282d6dfc7726fc08cc00058d9a7f
> 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
> Assignee: Etienne Chauchot
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> pull-request-available, reactive
>
> 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.20.10#820010)
