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/05/10 14:25:00 UTC
[jira] [Closed] (FLINK-9324) SingleLogicalSlot returns completed
release future before slot is properly returned
[ https://issues.apache.org/jira/browse/FLINK-9324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann closed FLINK-9324.
--------------------------------
Resolution: Fixed
Fixed via
master: c7eb6acaf95a6656ec6bd0a0b401c1944473e7f2
1.5.0: 7470b96536f8471855a43ce6f1856cec4bb9fbea
> SingleLogicalSlot returns completed release future before slot is properly returned
> -----------------------------------------------------------------------------------
>
> Key: FLINK-9324
> URL: https://issues.apache.org/jira/browse/FLINK-9324
> Project: Flink
> Issue Type: Bug
> Components: Distributed Coordination
> Affects Versions: 1.5.0, 1.6.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Blocker
> Labels: flip-6
> Fix For: 1.5.0
>
>
> The {{SingleLogicalSlot#releaseSlot}} method returns a future which is completed once the slot has been returned to the {{SlotOwner}}. Unfortunately, we don't wait for the {{SlotOwner's}} response to complete the future but complete it directly after the call has been made. This causes that the {{ExecutionGraph}} can get restarted in case of a recovery before all of its slots have been returned to the {{SlotPool}}. As a consequence, the allocation of the new tasks might require more than the max parallelism because of collisions with old tasks (in case of slot sharing).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)