[
https://issues.apache.org/jira/browse/FLINK-36673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896744#comment-17896744
]
Yaroslav Tkachenko commented on FLINK-36673:
--------------------------------------------
{quote}The problem seems to be that checkpointing is not enabled at all, not
that there is no savepoint
{quote}
Checkpointing is enabled as a very last step when building the execution graph.
If the job fails before that (e.g. when registering a source or a sink), the
Flink runtime will return the "Checkpointing has not been enabled" exception.
> Operator is not properly handling failed deployments without savepoints
> -----------------------------------------------------------------------
>
> Key: FLINK-36673
> URL: https://issues.apache.org/jira/browse/FLINK-36673
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Reporter: Yaroslav Tkachenko
> Priority: Major
> Attachments: stacktrace.txt
>
>
> I noticed an issue after upgrading Flink Kubernetes Operator from 1.9 to 1.10.
> When I deploy a FlinkDeployment that fails during the startup, I get a
> "ReconciliationException: Could not observe latest savepoint information"
> (full stacktrace is attached).
> I think the issue was introduced here:
> [https://github.com/apache/flink-kubernetes-operator/pull/871.]
> *AbstractFlinkService.getLastCheckpoint* now throws a
> *ReconciliationException* when a savepoint is not available, and
> *SnapshotObserver.observeLatestCheckpoint* doesn't handle it properly. I
> think having no savepoint is completely normal in some situations (e.g. a
> brand new job).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
