[
https://issues.apache.org/jira/browse/FLINK-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16346773#comment-16346773
]
Till Rohrmann commented on FLINK-8042:
--------------------------------------
I think one way to tackle this problem is to enhance the {{RestartStrategy}}
interface to be able to detect and handle different situations (e.g.
{{NoResourceAvailableException}} vs. regular job failure). That way we could
implement more elaborate behaviour where we allow certain failures too occur
several times before falling back to a full restart, for example.
I'm not sure whether this will make it into 1.5.0 because it requires some more
brain cycles on how to design the proper interface.
> Retry individual failover-strategy for some time first before reverting to
> full job restart
> -------------------------------------------------------------------------------------------
>
> Key: FLINK-8042
> URL: https://issues.apache.org/jira/browse/FLINK-8042
> Project: Flink
> Issue Type: Bug
> Components: ResourceManager, State Backends, Checkpointing
> Affects Versions: 1.3.2
> Reporter: Steven Zhen Wu
> Priority: Blocker
> Fix For: 1.5.0
>
>
> Let's we will a taskmanager node. When Flink tries to attempt fine grained
> recovery and fails replacement taskmanager node didn't come back in time, it
> reverts to full job restart.
> Stephan and Till was suggesting that Flink can/should retry fine grained
> recovery for some time before giving up and reverting full job restart
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
