[
https://issues.apache.org/jira/browse/FLINK-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16354124#comment-16354124
]
Monal Daxini commented on FLINK-8042:
-------------------------------------
This bug is quite detrimental to workloads where there is large state and is
massively parallel. This is potential blocker for one of our use cases. Causing
a full job restart takes while to recover.
With local state recovery (potentially targeted for 1.5) and running the job
with 1 or 2 extra TaskManagers might mitigate this to an extent. However, does
not solve the problem.
It would be good to address this sooner than later. Do we have a design doc
that outlines the interface changes, if not can we please start one.
> 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)
