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 2020/08/14 17:46:00 UTC

[jira] [Closed] (FLINK-18935) CompletedOperationCache accepts new operations after closeAsync has been called

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

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

Fixed via 61caf2ea139684f216df873ed3b864b6cb9d4a4f

> CompletedOperationCache accepts new operations after closeAsync has been called
> -------------------------------------------------------------------------------
>
>                 Key: FLINK-18935
>                 URL: https://issues.apache.org/jira/browse/FLINK-18935
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / REST
>    Affects Versions: 1.10.1, 1.12.0, 1.11.1
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.12.0
>
>
> The {{CompletedOperationCache}} accepts new operations after {{closeAsync}} has been called. This is problematic because the returned termination future of {{closeAsync}} won't include these new operations. I think it would be better to fail with an {{IllegalStateException}} when one tries to enqueue a new operation after the {{CompletedOperationCache}} has been shut down.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)