[
https://issues.apache.org/jira/browse/FLINK-27802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542910#comment-17542910
]
Gyula Fora commented on FLINK-27802:
------------------------------------
that's true, but people generally look at the logs of the last attempt first
which at this point will have no information.
> Savepoint restore errors are swallowed for Flink 1.15
> -----------------------------------------------------
>
> Key: FLINK-27802
> URL: https://issues.apache.org/jira/browse/FLINK-27802
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.0.0
> Reporter: Gyula Fora
> Priority: Critical
>
> When a job is submitted with an incorrect savepoint path the error is
> swallowed by Flink due to the result store:
> 2022-05-26 12:34:43,497 WARN
> org.apache.flink.runtime.dispatcher.StandaloneDispatcher [] - Ignoring
> JobGraph submission 'State machine job' (00000000000000000000000000000000)
> because the job already reached a globally-terminal state (i.e. FAILED,
> CANCELED, FINISHED) in a previous execution.
> 2022-05-26 12:34:43,552 INFO
> org.apache.flink.client.deployment.application.ApplicationDispatcherBootstrap
> [] - Application completed SUCCESSFULLY
> The easiest way to reproduce this is to create a new deployment and set
> initialSavepointPath to a random missing path.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
