You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2023/07/19 14:48:00 UTC
[jira] [Closed] (FLINK-32589) Carry over parallelism overrides to prevent users from clearing them on updates
[ https://issues.apache.org/jira/browse/FLINK-32589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gyula Fora closed FLINK-32589.
------------------------------
Fix Version/s: kubernetes-operator-1.6.0
Resolution: Fixed
merged to main 9fe68251eb1a37333a6e862bf7b048061396498c
> 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
> Assignee: Gyula Fora
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.6.0
>
>
> 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)