You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Zhu Zhu (Jira)" <ji...@apache.org> on 2019/09/19 15:30:00 UTC
[jira] [Updated] (FLINK-14131) Support choosing new version
failover strategy via configuration
[ https://issues.apache.org/jira/browse/FLINK-14131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhu Zhu updated FLINK-14131:
----------------------------
Description:
FLINK-10429 introduces new version failover strategies.
There are two different new version failover strategies and can be more in the future.
Users should be able to choose the proper strategy for their jobs via configuration.
A discussion(maybe a related survey and FLIP) should be conducted first to decide whether to respect the existing "jobmanager.execution.failover-strategy" config, or we can just deprecate the restart-all strategy.
was:
FLINK-10429 introduces new version failover strategies.
There are two different new version failover strategies and can be more in the future.
Users should be able to choose the proper strategy for their jobs via configuration.
> Support choosing new version failover strategy via configuration
> ----------------------------------------------------------------
>
> Key: FLINK-14131
> URL: https://issues.apache.org/jira/browse/FLINK-14131
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.10.0
> Reporter: Zhu Zhu
> Priority: Major
> Fix For: 1.10.0
>
>
> FLINK-10429 introduces new version failover strategies.
> There are two different new version failover strategies and can be more in the future.
> Users should be able to choose the proper strategy for their jobs via configuration.
> A discussion(maybe a related survey and FLIP) should be conducted first to decide whether to respect the existing "jobmanager.execution.failover-strategy" config, or we can just deprecate the restart-all strategy.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)