[
https://issues.apache.org/jira/browse/FLINK-30463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maximilian Michels closed FLINK-30463.
--------------------------------------
Resolution: Fixed
> Stabilization period starts before job goes into RUNNING
> ---------------------------------------------------------
>
> Key: FLINK-30463
> URL: https://issues.apache.org/jira/browse/FLINK-30463
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.4.0
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.4.0
>
>
> We are tracking the stabilization period from the job start time which can
> greatly vary from the time the job goes into RUNNING state. This can result
> in no stabilization period at all leading to poor scaling decisions.
> Thus, we should change the logic to use the update time in combination with a
> RUNNING job status.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)