There is an expected case where this might happen:
if too much time has elapsed since the savepoint was completed (default
5 minutes; controlled by rest.async.store-duration)
Did this happen earlier than that?
On 16/06/2022 15:53, Peter Westermann wrote:
We recently upgraded one of our Flink clusters to version 1.15.0 and
are now seeing sporadic issues when stopping a job with a savepoint
via the REST API. This happens for */jobs/:jobid/savepoints
*and*/jobs/:jobid/stop*:
The job finishes with a savepoint but the triggerId returned from the
REST API seems to be invalid. Any lookups via
*/jobs/:jobid/savepoints/:triggerid* fail with a 404 and the following
error:
org.apache.flink.runtime.rest.handler.RestHandlerException: There is
no savepoint operation with triggerId=cee5054245598efb42245b3046a6ae75
for job 0995a9461f0178294ea71c9accbe750c
Peter Westermann
Analytics Software Architect
cidimage001.jpg@01D78D4C.C00AC080
peter.westerm...@genesys.com <mailto:peter.westerm...@genesys.com>
cidimage001.jpg@01D78D4C.C00AC080
cidimage002.jpg@01D78D4C.C00AC080 <http://www.genesys.com/>
