[
https://issues.apache.org/jira/browse/FLINK-37872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyula Fora reassigned FLINK-37872:
----------------------------------
Assignee: Sai Sharath Dandi
> Autoscaler computes negative true processing rate
> -------------------------------------------------
>
> Key: FLINK-37872
> URL: https://issues.apache.org/jira/browse/FLINK-37872
> Project: Flink
> Issue Type: Bug
> Components: Autoscaler
> Reporter: Sai Sharath Dandi
> Assignee: Sai Sharath Dandi
> Priority: Major
> Attachments: Screenshot 2025-05-29 at 3.26.31 PM.png
>
>
> After a scale up/down, autoscaler measures the true processing rate via busy
> time metrics to be negative as it uses num-records-in metric before the scale
> up/down -
> [https://github.com/apache/flink-kubernetes-operator/blob/main/flink-autoscaler/src/main/java/org/apache/flink/autoscaler/ScalingMetricEvaluator.java#L459]
>
> We need to find the first metric after the last scaling action instead to
> compute the true processing rate
>
> !Screenshot 2025-05-29 at 3.26.31 PM.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)