[
https://issues.apache.org/jira/browse/FLINK-30920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Miglani updated FLINK-30920:
-----------------------------------
Description:
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
was: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
> 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
>
> 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)
