You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2017/07/23 14:30:01 UTC

[jira] [Resolved] (FLINK-7231) SlotSharingGroups are not always released in time for new restarts

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

Stephan Ewen resolved FLINK-7231.
---------------------------------
      Resolution: Fixed
    Release Note: 
Fixed in
  - 1.4.0 via 605319b550aeba5612b0e32fa193521081b7adc5
  - 1.3.2 via 39f5b1144167dcb80e8708f4cb5426e76f648026

> SlotSharingGroups are not always released in time for new restarts
> ------------------------------------------------------------------
>
>                 Key: FLINK-7231
>                 URL: https://issues.apache.org/jira/browse/FLINK-7231
>             Project: Flink
>          Issue Type: Bug
>          Components: Distributed Coordination
>    Affects Versions: 1.3.1
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>            Priority: Blocker
>             Fix For: 1.4.0, 1.3.2
>
>
> In the case where there are not enough resources to schedule the streaming program, a race condition can lead to a sequence of the following errors:
> {code}
> java.lang.IllegalStateException: SlotSharingGroup cannot clear task assignment, group still has allocated resources.
> {code}
> This eventually recovers, but may involve many fast restart attempts before doing so.
> The root cause is that slots are not cleared before the next restart attempt.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)