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/07/23 22:10:00 UTC
[jira] [Closed] (FLINK-9910) Non-queued scheduling failure
sometimes does not return the slot
[ https://issues.apache.org/jira/browse/FLINK-9910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann closed FLINK-9910.
--------------------------------
Resolution: Fixed
Fixed via
master: 0180d068565d99db1db998944686064ceddf398f
1.6.0: 4608f67df61d58569e229db04590b161c014c8a0
1.5.2: 7f24e840bbf4beb09826ecc32c05fcf9b470982a
> Non-queued scheduling failure sometimes does not return the slot
> ----------------------------------------------------------------
>
> Key: FLINK-9910
> URL: https://issues.apache.org/jira/browse/FLINK-9910
> Project: Flink
> Issue Type: Bug
> Components: Distributed Coordination
> Affects Versions: 1.5.1, 1.6.0, 1.7.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.5.2, 1.6.0
>
>
> Similar to FLINK-9908, it can happen that in case of a non-queued scheduling failure a slot is not properly returned to the {{SlotPool}}. The reason for the failure seems to be the exceptional completion of the {{allocationFuture}} in {{Execution#scheduleForExecution}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)