You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (Jira)" <ji...@apache.org> on 2020/08/28 15:13:00 UTC
[jira] [Resolved] (FLINK-19045) Remove obsolete option
'taskmanager.network.partition.force-release-on-consumption'
[ https://issues.apache.org/jira/browse/FLINK-19045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephan Ewen resolved FLINK-19045.
----------------------------------
Resolution: Fixed
Fixed for 1.12 via 3ad06e3aacda3923f3c8e40eced430177aecb49d
> Remove obsolete option 'taskmanager.network.partition.force-release-on-consumption'
> -----------------------------------------------------------------------------------
>
> Key: FLINK-19045
> URL: https://issues.apache.org/jira/browse/FLINK-19045
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Network
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Priority: Major
> Fix For: 1.12.0
>
>
> This option was a fallback/safeguard option introduced when the fine-grained failover for batch was added.
> With the fine-grained batch failover, the batch result partitions were no longer immediately cleaned up, but retained for recovery until the scheduler decided that they were no longer needed.
> The purpose of the flag was to restore the old "immediate cleanup" behavior should it be needed.
> The batch failover has proven stable and this fallback option can be removed now.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)