[
https://issues.apache.org/jira/browse/FLINK-17977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17133500#comment-17133500
]
Robert Metzger commented on FLINK-17977:
----------------------------------------
Thanks for your assessment. I would probably keep the name "checkpoint" around
in the logs everywhere, but in the CheckpointCoordinator "Triggering
Checkpoint" message, I would extend it to something like "Triggering Checkpoint
(type=SAVEPOINT)". Based on the ID, you can follow it through the system
(including the TaskManagers).
> Check log sanity
> ----------------
>
> Key: FLINK-17977
> URL: https://issues.apache.org/jira/browse/FLINK-17977
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.11.0
> Reporter: Till Rohrmann
> Assignee: Chesnay Schepler
> Priority: Critical
> Labels: pull-request-available, release-testing
> Fix For: 1.11.0
>
>
> Run a normal Flink workload (e.g. job with fixed number of failures on
> session cluster) and check that the produced Flink logs make sense and don't
> contain confusing statements.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
