[ https://issues.apache.org/jira/browse/FLINK-34178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rui Fan resolved FLINK-34178. ----------------------------- Fix Version/s: kubernetes-operator-1.8.0 Resolution: Fixed > The ScalingTracking of autoscaler is wrong > ------------------------------------------ > > Key: FLINK-34178 > URL: https://issues.apache.org/jira/browse/FLINK-34178 > Project: Flink > Issue Type: Bug > Components: Autoscaler > Affects Versions: kubernetes-operator-1.8.0 > Reporter: Rui Fan > Assignee: Rui Fan > Priority: Major > Labels: pull-request-available > Fix For: kubernetes-operator-1.8.0 > > > The ScalingTracking of autoscaler is wrong, it's always greater than > AutoScalerOptions#STABILIZATION_INTERVAL. > h2. Reason: > When flink job isStabilizing, ScalingMetricCollector#updateMetrics will > return a empty metric history. In the JobAutoScalerImpl#runScalingLogic > method, if `collectedMetrics.getMetricHistory().isEmpty()` , we don't update > the ScalingTracking. > > The default value of AutoScalerOptions#STABILIZATION_INTERVAL is 5 min, so > the restartTime is always greater than 5 min. > However, it's quick when we use rescale api. -- This message was sent by Atlassian Jira (v8.20.10#820010)