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/03/13 17:20:00 UTC

[jira] [Closed] (FLINK-8934) Cancel slot requests for otherwisely fulfilled requests

     [ https://issues.apache.org/jira/browse/FLINK-8934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann closed FLINK-8934.
--------------------------------
    Resolution: Fixed

Fixed via

1.6.0: 445cdfd57941c4c888a6e73356558fd5f11d443c

1.5.0: 9551c6fa91bc1cc12352c9fe8464b5baf868268e

> Cancel slot requests for otherwisely fulfilled requests
> -------------------------------------------------------
>
>                 Key: FLINK-8934
>                 URL: https://issues.apache.org/jira/browse/FLINK-8934
>             Project: Flink
>          Issue Type: Bug
>          Components: Distributed Coordination
>    Affects Versions: 1.5.0, 1.6.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Critical
>              Labels: flip-6
>             Fix For: 1.5.0, 1.6.0
>
>
> If a slot request is fulfilled with a different allocation id, then we should cancel the other slot request at the {{ResourceManager}}. Otherwise we might have some stale slot requests which first need to time out before slots are available again.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)