You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Andrey Zagrebin (JIRA)" <ji...@apache.org> on 2019/01/15 16:32:02 UTC
[jira] [Comment Edited] (FLINK-10724) Refactor failure handling in
check point coordinator
[ https://issues.apache.org/jira/browse/FLINK-10724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16743199#comment-16743199 ]
Andrey Zagrebin edited comment on FLINK-10724 at 1/15/19 4:31 PM:
------------------------------------------------------------------
Hi [~yanghua], I think it is better to find a committer to shepherd this effort.
I can help with reviewing the implementation but I cannot merge it because I am not a committer.
Maybe, [~thw] could help with it, he created the duplicated issue.
was (Author: azagrebin):
Hi [~yanghua], I think it is better to find a committer to shepherd this effort.
I can help with reviewing the implementation but I cannot merge it because I am not a committer.
> 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-4810.
> See also discussion here: [https://github.com/apache/flink/pull/6567]
> The specific design document : https://docs.google.com/document/d/1ce7RtecuTxcVUJlnU44hzcO2Dwq9g4Oyd8_biy94hJc/edit?usp=sharing
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)