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

vinoyang commented on FLINK-10074:
----------------------------------

[~thw] I personally prefer that once JM failover, the counter will reset. I 
don't think it's necessary to introduce too much complexity for this. If we 
need to maintain a global counter across JM processes, we will use third-party 
components such as zookeeper. I think it is appropriate to maintain this 
counter for the life of a JM process. Once JM failover, the Job will be 
restored (re-deployed, run), and it is reasonable to reset the counter for a 
new runtime environment.

> Allowable number of checkpoint failures 
> ----------------------------------------
>
>                 Key: FLINK-10074
>                 URL: https://issues.apache.org/jira/browse/FLINK-10074
>             Project: Flink
>          Issue Type: Improvement
>          Components: State Backends, Checkpointing
>            Reporter: Thomas Weise
>            Assignee: vinoyang
>            Priority: Major
>
> For intermittent checkpoint failures it is desirable to have a mechanism to 
> avoid restarts. If, for example, a transient S3 error prevents checkpoint 
> completion, the next checkpoint may very well succeed. The user may wish to 
> not incur the expense of restart under such scenario and this could be 
> expressed with a failure threshold (number of subsequent checkpoint 
> failures), possibly combined with a list of exceptions to tolerate.
>  



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

Reply via email to