You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2019/10/08 09:44:00 UTC
[jira] [Closed] (FLINK-14271) Remove legacy
RestartPipelinedRegionStrategy
[ https://issues.apache.org/jira/browse/FLINK-14271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler closed FLINK-14271.
------------------------------------
Resolution: Fixed
master: c5c59feec0ed8a0ac5213802d79956c815a2b812
> Remove 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
> Assignee: Zhu Zhu
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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.
> Since it is basically broken and is not a public interface(the failover config "region" now points to AdaptedRestartPipelinedRegionStrategyNG), it's safe to remove it.
> I'd propose to remove the legacy {{RestartPipelinedRegionStrategy}} components to reduce efforts for further changes on flink runtime.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)