You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2023/01/05 09:07:00 UTC

[jira] [Closed] (FLINK-30466) Detect ineffective scaling operations

     [ https://issues.apache.org/jira/browse/FLINK-30466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gyula Fora closed FLINK-30466.
------------------------------
    Resolution: Won't Fix

I am closing this in order to replace with some more concrete tasks around scaling decisions. This ticket was too broad

> Detect ineffective scaling operations
> -------------------------------------
>
>                 Key: FLINK-30466
>                 URL: https://issues.apache.org/jira/browse/FLINK-30466
>             Project: Flink
>          Issue Type: New Feature
>          Components: Kubernetes Operator
>            Reporter: Gyula Fora
>            Assignee: Matyas Orhidi
>            Priority: Major
>
> The autoscaler logic currently does not consider whether a given proposed parallelism change will achieve the desired processing rate based on historic metrics.
> It might be possible that we are for example trying to scale down to a parallelism that we have also done in the past which resulted in an immediate scale up.
> This could be avoided by comparing the expected processing rate at a certain parallelism with past metrics from that parallelism setting. There should be some flexibility and a limited "memory" but some simple checks could reduce instable scaling caused by non-linear performance changes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)