[
https://issues.apache.org/jira/browse/FLINK-27804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542984#comment-17542984
]
Gyula Fora commented on FLINK-27804:
------------------------------------
The problem is that I cannot reliably say what the root cause was and whether
this will solve it 100%
We will keep testing this today and if we don't hit this again during another
day of functional testing I think it would be better to create an RC3 including
this fix.
> Do not observe cluster/job mid upgrade
> --------------------------------------
>
> Key: FLINK-27804
> URL: https://issues.apache.org/jira/browse/FLINK-27804
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.0.0
> Reporter: Gyula Fora
> Assignee: Gyula Fora
> Priority: Critical
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.0.0
>
>
> Seems like in some weird cornercases when we observe the FINISHED job
> (stopped with savepoint) during an upgrade the recorded last snapshot is
> incorrect (still need to investigate if this is due to a Flink problem or
> what) This can lead to upgrade errors.
> This can be avoided by simply skipping the observe step when the
> reconciliation status is UPGRADING because at that point we actually know
> that the job was already shut down and state recorded correctly in the
> savepoint info.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
