You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Maximilian Michels (Jira)" <ji...@apache.org> on 2023/04/19 14:51:00 UTC

[jira] [Updated] (FLINK-30920) K8 cluster autoscaler | exclude operator ids from scaler

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

Maximilian Michels updated FLINK-30920:
---------------------------------------
    Fix Version/s: kubernetes-operator-1.5.0

> K8 cluster autoscaler | exclude operator ids from scaler
> --------------------------------------------------------
>
>                 Key: FLINK-30920
>                 URL: https://issues.apache.org/jira/browse/FLINK-30920
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Gaurav Miglani
>            Assignee: Gaurav Miglani
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: kubernetes-operator-1.5.0
>
>         Attachments: sample-logs
>
>
> Sometime in cases of sink operator ids, where logic is heavy group aggregation and scan mode is earliest, flink k8 operator tries to scale/downscale sink operator ids as well, there should be a way where user can give list of operator ids/vertices where cluster autoscaler doesn't perform any scaling action on a configurable list of operator ids/vertices
>  



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