The logs would have helped to understand better what you were doing.
The stacktrace you shared indicates that you either asked for the status of
a savepoint creation that had already been completed and was, therefore,
removed from the operations cache or you used some job ID/request ID
pair that w
Thanks for your reply. I'm using the flink docker
image flink:1.12.2-scala_2.11-java8. Yes, the folder was created in S3. I
took a look at the UI and it showed the following:
*Latest Restore ID: 49Restore Time: 2021-03-31 09:37:43Type:
CheckpointPath:
s3:fcc82deebb4565f31a7f63989939c463/chk
Hi Claude,
thanks for reaching out to the Flink community. Could you provide the Flink
logs for this run to get a better understanding of what's going on?
Additionally, what exact Flink 1.12 version are you using? Did you also
verify that the snapshot was created by checking the actual folder?
Bes
Hello,
I have Flink setup as an Application Cluster in Kubernetes, using Flink
version 1.12. I created a savepoint using the curl command and the status
indicated it was completed. I then tried to relaunch the job from that
save point using the following arguments as indicated in the doc found
h
