[
https://issues.apache.org/jira/browse/FLINK-14271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943374#comment-16943374
]
Zhu Zhu commented on FLINK-14271:
---------------------------------
Thanks [~stevenz3wu] for the information! We can remove the legacy
{{RestartPipelinedRegionStrategy}} then.
For your information, the "{{individual}}" failover strategy will be deprecated
in Flink 1.10 since it is also superseded by the new region failover
strategy({{AdaptedRestartPipelinedRegionStrategyNG}}) which also supports fine
grained recovery for embarrassingly parallel jobs. And the "{{individual}}"
failover strategy may not be supported in the new scheduler.
To use Flink 1.10, you can either stick to the legacy scheduler which still
supports "individual" failover strategy, or turn to the "region" failover
strategy.
> Deprecate legacy RestartPipelinedRegionStrategy
> -----------------------------------------------
>
> Key: FLINK-14271
> URL: https://issues.apache.org/jira/browse/FLINK-14271
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.10.0
> Reporter: Zhu Zhu
> Priority: Minor
> Fix For: 1.10.0
>
>
> The legacy {{RestartPipelinedRegionStrategy}} has been superseded by
> {{AdaptedRestartPipelinedRegionStrategyNG}} in Flink 1.9.
> It heavily depends on ExecutionGraph components and becomes a blocker for a
> clean scheduler re-architecture.
> We should deprecate it for further removal.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
