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 2019/07/10 20:54:00 UTC
[jira] [Resolved] (FLINK-12736) ResourceManager may release TM with
allocated slots
[ https://issues.apache.org/jira/browse/FLINK-12736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann resolved FLINK-12736.
-----------------------------------
Resolution: Fixed
Fixed via
1.9.0: 5c762cec46
1.8.2: 48f5c78177abb322ba6a7d60f375973f22831146
1.7.3: 9069f4dd82df715bf50a2bc45b968283c161f98b
> ResourceManager may release TM with allocated slots
> ---------------------------------------------------
>
> Key: FLINK-12736
> URL: https://issues.apache.org/jira/browse/FLINK-12736
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.7.2, 1.8.1, 1.9.0
> Reporter: Chesnay Schepler
> Assignee: Andrey Zagrebin
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.7.3, 1.8.2, 1.9.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The {{ResourceManager}} looks out for TaskManagers that have not had any slots allocated on them for a while, as these could be released to safe resources. If such a TM is found the RM checks via an RPC call whether the TM still holds any partitions. If no partition is held then the TM is released.
> However, in the RPC callback no check is made whether the TM is actually _still_ idle. In the meantime a slot could've been allocated on the TM.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)