[
https://issues.apache.org/jira/browse/FLINK-30920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17685390#comment-17685390
]
Gaurav Miglani commented on FLINK-30920:
----------------------------------------
I think it is vertex id, as i can see in logs, [~mxm] correct me if i'm wrong,
https://github.com/apache/flink-kubernetes-operator/blob/main/flink-kubernetes-operator/src/main/java/org/apache/flink/kubernetes/operator/autoscaler/ScalingExecutor.java#L140
> 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)
