flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Rohrmann (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (FLINK-9047) SlotPool can fail to release slots
Date Thu, 22 Mar 2018 08:52:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16409235#comment-16409235

Till Rohrmann edited comment on FLINK-9047 at 3/22/18 8:51 AM:

Sorry [~sihuazhou], I saw your comment too late. But maybe you could review my PR.

was (Author: till.rohrmann):
Sorry [~sihuazhou], I saw your comment to late. But maybe you could review my PR.

> SlotPool can fail to release slots
> ----------------------------------
>                 Key: FLINK-9047
>                 URL: https://issues.apache.org/jira/browse/FLINK-9047
>             Project: Flink
>          Issue Type: Bug
>          Components: Distributed Coordination
>    Affects Versions: 1.5.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Blocker
>              Labels: flip-6
>             Fix For: 1.5.0
> The {{SlotPool}} releases idling slots. If the release operation fails (e.g. timeout),
then it simply continues using the slot. This is problematic if the owning {{TaskExecutor}}
failed before and was unregistered in the meantime from the {{SlotPool}}. As a result, the
{{SlotPool}} will reuse the slot and whenever it tries to return because it is idling it will
fail again. This, effectively, renders the scheduling of a job impossible.

This message was sent by Atlassian JIRA

View raw message