[FLINK-11190] Log stack trace on declined/discarded checkpoint

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Duplicate

Environment

Flink 1.5.2

• Assignee: boshu Zheng
• Reporter: Daniel Harper
• Created: 18/Dec/18 09:41
• Updated: 13/Apr/21 20:40
• Resolved: 20/Dec/18 09:27

Description

When setting the configuration failOnCheckpointingErrors, any checkpoints that are declined don't appear to print the stack trace for the exception that was thrown.

The current code appears to print a descriptive message, but not the actual underlying cause of why the checkpoint failed in the first place.

https://github.com/apache/flink/blob/release-1.5.2/flink-runtime/src/main/java/org/apache/flink/runtime/checkpoint/CheckpointCoordinator.java#L1255

This would be useful for trying to determine reasons for failure so we can take steps to improve the reliability of checkpointing (even though the setting 'failOnCheckpointingErrors' is set, it would still be useful to see the causes of checkpoint failures)

Issue Links

• duplicates: FLINK-10753 Propagate and log snapshotting exceptions