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/06/14 12:38:00 UTC

[jira] [Resolved] (FLINK-11059) JobMaster may continue using an invalid slot if releasing idle slot meet a timeout

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

Till Rohrmann resolved FLINK-11059.
-----------------------------------
    Resolution: Fixed

Fixed via
1.9.0: a4865cd67239c938e0075bcc2b112b944cc3c249
1.8.1: 5ef79de88726ddfccee30cb34a22711ca2b1116f
1.7.3: 65b6f99a69dbe65fc2dfaa97d0662f76909ef371

> JobMaster may continue using an invalid slot if releasing idle slot meet a timeout
> ----------------------------------------------------------------------------------
>
>                 Key: FLINK-11059
>                 URL: https://issues.apache.org/jira/browse/FLINK-11059
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination
>    Affects Versions: 1.7.0
>            Reporter: shuai.xu
>            Assignee: shuai.xu
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.7.3, 1.9.0, 1.8.1
>
>
> When job master releases an idle slot to task executor, it may meet a timeout exception which cause that task executor may have already released the slot, but job master will add the slot back to available slots, and the slot may be used again. Then job master will continue deploying task to the slot, but task executor does not recognize it.



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