You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Daniel Harper (JIRA)" <ji...@apache.org> on 2018/12/18 09:42:00 UTC

[jira] [Updated] (FLINK-11190) Log stack trace on declined/discarded checkpoint

     [ https://issues.apache.org/jira/browse/FLINK-11190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Harper updated FLINK-11190:
----------------------------------
    Summary: Log stack trace on declined/discarded checkpoint  (was: Log stack trace on declined checkpoint)

> Log stack trace on declined/discarded checkpoint
> ------------------------------------------------
>
>                 Key: FLINK-11190
>                 URL: https://issues.apache.org/jira/browse/FLINK-11190
>             Project: Flink
>          Issue Type: Improvement
>         Environment: Flink 1.5.2
>            Reporter: Daniel Harper
>            Priority: Trivial
>
> When setting the configuration [failOnCheckpointingErrors|https://github.com/apache/flink/blob/master/flink-streaming-java/src/main/java/org/apache/flink/streaming/api/environment/CheckpointConfig.java#L248], 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) 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)