[
https://issues.apache.org/jira/browse/FLINK-26916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514589#comment-17514589
]
David Morávek commented on FLINK-26916:
---------------------------------------
This has been a known struggle for quite some time. In the past this has been
worked around by custom HA services, which is very inconvenient because it
brings an additional dependency to the Flink runtime. One approach that we were
thinking of recently was extending the JRS so the stored job result contains
list of retained checkpoints. This of course implies that cluster gets shut
down / job gets terminated properly (other cases should be used for fail-over
scenarios only).
> 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: Yang Wang
> Priority: Blocker
> Labels: pull-request-available
> Fix For: kubernetes-operator-0.1.0
>
>
> RC: The old jobgraph is being reused when resuming
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
