[
https://issues.apache.org/jira/browse/FLINK-21883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21883:
-----------------------------------
Labels: auto-deprioritized-major reactive stale-minor (was:
auto-deprioritized-major reactive)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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
> Priority: Minor
> Labels: auto-deprioritized-major, reactive, stale-minor
>
> 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)
