[
https://issues.apache.org/jira/browse/FLINK-18955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arvid Heise closed FLINK-18955.
-------------------------------
Fix Version/s: (was: 1.10.3)
(was: 1.11.2)
Resolution: Fixed
Merged into master as
[3b1b77e5611fb2ff77a2515c676b3299964a0d5a|https://github.com/apache/flink/commit/3b1b77e5611fb2ff77a2515c676b3299964a0d5a].
> Add snapshot path to job startup message
> ----------------------------------------
>
> Key: FLINK-18955
> URL: https://issues.apache.org/jira/browse/FLINK-18955
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Checkpointing
> Affects Versions: 1.10.1, 1.12.0, 1.11.1
> Reporter: Nico Kruber
> Assignee: Yuan Mei
> Priority: Major
> Labels: pull-request-available, usability
> Fix For: 1.12.0
>
>
> When a job is started from a checkpoint or savepoint (I'm using snapshot as
> the unanimous term below), the {{CheckpointCoordinator}} prints a log line
> like this:
> {code}
> 2020-08-13 13:50:51,418 INFO
> org.apache.flink.runtime.checkpoint.CheckpointCoordinator [] - Restoring
> job 220d8a4953cd40198b6eb3b1ec0cece0 from latest valid checkpoint: Checkpoint
> 357 @ 1597326576925 for 220d8a4953cd40198b6eb3b1ec0cece0.
> {code}
> I propose to add the path to the snapshot to this message because which
> snapshot is taken for restore may actually not be that obvious for the user:
> even if a savepoint was specified in the job start command, e.g. in a
> Kubernetes pod spec, an HA store could overrule the decision and take a more
> recent snapshot instead. If that snapshot is a savepoint, it is not that easy
> to map this to checkpoint IDs and find out which savepoint the job actually
> started from.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
