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 2020/04/24 10:14:00 UTC
[jira] [Closed] (FLINK-10505) Treat fail signal as scheduling event
[ https://issues.apache.org/jira/browse/FLINK-10505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann closed FLINK-10505.
---------------------------------
Resolution: Later
This issue is quite outdated and needs to be updated once the design for declarative resource management and the reactive mode has been accepted.
> Treat fail signal as scheduling event
> -------------------------------------
>
> Key: FLINK-10505
> URL: https://issues.apache.org/jira/browse/FLINK-10505
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.7.0
> Reporter: Till Rohrmann
> Priority: Major
>
> Instead of simply calling into the {{RestartStrategy}} which restarts the existing {{ExecutionGraph}} with the same parallelism, the {{ExecutionGraphDriver}} should treat a recovery similar to the initial scheduling operation. First, one needs to decide on the new parallelism of the {{ExecutionGraph}} (scale up/scale down) wrt to the available set of resources. Only if the minimum configuration is fulfilled, the potentially rescaled {{ExecutionGraph}} will be restarted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)