[
https://issues.apache.org/jira/browse/FLINK-26916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514479#comment-17514479
]
Gyula Fora commented on FLINK-26916:
------------------------------------
After discussing with [~wangyang0918] there seems to be a simple fix for the
Kubernetes HA case by simply deleting the jobgraph data before deployment. This
will cause flink to always regenerate the job. promoting this to blocker with
this in mind
> The Operator ignores job related changes (jar, parallelism) during last-state
> upgrades
> --------------------------------------------------------------------------------------
>
> Key: FLINK-26916
> URL: https://issues.apache.org/jira/browse/FLINK-26916
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-0.1.0, kubernetes-operator-1.0.0
> Reporter: Matyas Orhidi
> Assignee: Gyula Fora
> Priority: Critical
> Labels: pull-request-available
>
> RC: The old jobgraph is being reused when resuming
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
