If I have a cancelled / terminated job for a clust...
# random
i
If I have a cancelled / terminated job for a cluster with HA enabled, what’s the easiest way to determine the location of the last retained checkpoint?
g
Go to the checkpoint directory and find the latest file
gratitude thank you 1
the HA metadata doesnt contain the checkpoint path in any human readable form unfortunately
also after cancelling the HA metadata is deleted
i
I also have s3 entropy enabled, would that make it more difficult finding the latest file?
g
I have no idea
y
Maybe we could improve this in the upstream Flink project. For example, store the latest retained checkpoint path in the JRS(job result store) along with job status.
g
That would be a great improvement for the operator functionality as well
1
y
cc @Matthias Maybe you are also interested.
m
Yes, I'm interested in getting this feature out. I'm happy to create a FLIP after I'm done with the leader election work (FLIP-285). But I would be also willing to help if someone else decides to pick it up earlier. 🙂
y
Maybe creating a dedicated FLIP for adding checkpoint location in JRS is an overkill.🤔
g
Yea, this is a relatively minor change with no side effects. I think no jira is necessary
m
might be. I haven't thought this through entirely. The idea is to merge the
ExecutionGraphInfoStore
and the
JobResultStore
into a single component/interface. IIRC, this might expose other meta information besides the
JobResult
in the latest checkpoint. This information (not only the checkpoint) might become useful to external projects. We might want to impose stricter policies on the data structure (making it @Public/@PublicEvolving API). That's why, I was thinking of a FLIP, initially.
y
Make sense. A stable API for external project is really important.