[
https://issues.apache.org/jira/browse/FLINK-32589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742865#comment-17742865
]
Maximilian Michels commented on FLINK-32589:
--------------------------------------------
We handle this in our application stack but I think this is something that the
operator should do for the user. Most users probably do a POST/PUT on the spec
which will clear any overrides. This will come as a surprise to users.
It is really an implementation detail that the overrides are handled via an
undocumented Flink configuration option. The overrides are more part of the
applications status than actual configuration.
Users can turn off autoscaling which should clear any overrides.
> Carry over parallelism overrides to prevent users from clearing them on
> updates
> -------------------------------------------------------------------------------
>
> Key: FLINK-32589
> URL: https://issues.apache.org/jira/browse/FLINK-32589
> Project: Flink
> Issue Type: Improvement
> Components: Autoscaler, Kubernetes Operator
> Reporter: Maximilian Michels
> Priority: Major
>
> The autoscaler currently sets the parallelism overrides via the Flink config
> {{pipeline.jobvertex-parallelism-overrides}}. Whenever the user posts specs
> updates, special care needs to be taken in order to carry over existing
> overrides. Otherwise the job will reset to the default parallelism
> configuration. Users shouldn't have to deal with this. Instead, whenever a
> new spec is posted which does not contain the overrides, the operator should
> automatically apply the last-used overrides (if autoscaling is enabled).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
