[
https://issues.apache.org/jira/browse/FLINK-30638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17675593#comment-17675593
]
Gyula Fora commented on FLINK-30638:
------------------------------------
I think the problem is that last-state mode uses simple checkpoint recovery
which ignores the flag. I think this will work if you switch to savepoint.
> Operator doesn't forward allowNonRestoredState flag
> ---------------------------------------------------
>
> Key: FLINK-30638
> URL: https://issues.apache.org/jira/browse/FLINK-30638
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.3.1
> Reporter: Alexis Sarda-Espinosa
> Priority: Critical
> Attachments: flink-kubernetes-operator_json.txt
>
>
> My Flink image is currently based on 1.15, and I'm using last-state upgrade
> mode, so I have HA enabled. I have set {{allowNonRestoredState}} as true.
> After an upgrade where I removed some transformations from the pipeline, I
> see the following exception in the deployed Flink cluster:
> Job 38585f46d840b3c2e9f843e230398d35 reached terminal state FAILED.
> org.apache.flink.runtime.client.JobInitializationException: Could not start
> the JobMaster.
> ...
> Caused by: java.util.concurrent.CompletionException:
> java.lang.IllegalStateException: There is no operator for the state
> d3bab17db5b56f81eb48b3e7d5cce15d
> I'm attaching some of the operator's logs, but I don't see anything strange
> there.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
