[ 
https://issues.apache.org/jira/browse/FLINK-30920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17684645#comment-17684645
 ] 

Gyula Fora commented on FLINK-30920:
------------------------------------

Could you please explain why it is a problem to downscale the sink? Maybe based 
on the metrics it seems that it doesn't need that much parallelism

> 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
>            Priority: Major
>         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)

Reply via email to