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 2018/09/17 13:54:00 UTC
[jira] [Closed] (FLINK-9912) Release TaskExecutors from SlotPool if
all slots have been removed
[ https://issues.apache.org/jira/browse/FLINK-9912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann closed FLINK-9912.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.7.0
Fixed via e3c98f05d3544d0165c2d97d2d00fcd295cef8c8
> Release TaskExecutors from SlotPool if all slots have been removed
> ------------------------------------------------------------------
>
> Key: FLINK-9912
> URL: https://issues.apache.org/jira/browse/FLINK-9912
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Coordination
> Affects Versions: 1.5.1, 1.6.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
>
> Currently, it is possible to fail slot allocations in the {{SlotPool}}. Failing an allocation means that the slot is removed from the {{SlotPool}}. If we have removed all slots from a {{TaskExecutor}}, then we should also release/close the connection to this {{TaskExecutor}}. At the moment, this only happens via the heartbeats if the {{TaskExecutor}} has become unreachable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)