[ 
https://issues.apache.org/jira/browse/FLINK-10724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16713973#comment-16713973
 ] 

vinoyang commented on FLINK-10724:
----------------------------------

Sorry, the reply is very late. Now I am planning to start this issue. I am 
going to introduce a {{CheckpointFailureReason}} (similar to 
{{CheckpointDeclineReason}}) to describe the reasons for various failures. What 
do you think? [~azagrebin] [~till.rohrmann]

> Refactor failure handling in check point coordinator
> ----------------------------------------------------
>
>                 Key: FLINK-10724
>                 URL: https://issues.apache.org/jira/browse/FLINK-10724
>             Project: Flink
>          Issue Type: Improvement
>          Components: State Backends, Checkpointing
>            Reporter: Andrey Zagrebin
>            Assignee: vinoyang
>            Priority: Major
>
> At the moment failure handling of asynchronously triggered checkpoint in 
> check point coordinator happens in different places. We could organise it 
> similar way as failure handling of synchronous triggering of checkpoint in 
> *CheckpointTriggerResult* where we classify error cases. This will simplify 
> e.g. integration of error counter for FLINK-10074.
> See also discussion here: [https://github.com/apache/flink/pull/6567]



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

Reply via email to