You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2018/06/27 13:13:00 UTC
[jira] [Closed] (FLINK-9634) Deactivate previous location based
scheduling if local recovery is disabled
[ https://issues.apache.org/jira/browse/FLINK-9634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann closed FLINK-9634.
--------------------------------
Resolution: Fixed
Fixed via
1.6.0: d5919d9c1d4054dbfa182e482e082940b4e2f24d
1.5.1: 4168d98522b32ffd946a460728a966cd13d62d08
> Deactivate previous location based scheduling if local recovery is disabled
> ---------------------------------------------------------------------------
>
> Key: FLINK-9634
> URL: https://issues.apache.org/jira/browse/FLINK-9634
> Project: Flink
> Issue Type: Bug
> Components: Distributed Coordination
> Affects Versions: 1.5.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0, 1.5.1
>
>
> With Flink 1.5.0 we introduced local recovery. In order to make local recovery work we had to change the scheduling to be aware of the previous location of the {{Execution}}. This scheduling strategy is also active if local recovery is deactivated. I suggest to also disable the scheduling strategy if local recovery is not enabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)