You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "David Morávek (Jira)" <ji...@apache.org> on 2023/03/09 13:11:00 UTC

[jira] [Resolved] (FLINK-31370) Cancellation of the StreamTask should prevent more timers from being fired

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

David Morávek resolved FLINK-31370.
-----------------------------------
    Fix Version/s: 1.18.0
       Resolution: Fixed

> Cancellation of the StreamTask should prevent more timers from being fired
> --------------------------------------------------------------------------
>
>                 Key: FLINK-31370
>                 URL: https://issues.apache.org/jira/browse/FLINK-31370
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Task
>            Reporter: David Morávek
>            Assignee: David Morávek
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.18.0
>
>
> If the task is canceled while the watermark progresses, it may be stuck in the Cancelling state for a long time (e.g., when many windows are firing). This is closely related to FLINK-20217, which might bring a more robust solution for checkpoint and cancellation code paths.
> As a stopgap solution, we'll introduce a check allowing InternalTimerService to break out of the firing loop if the StreamTask has been marked as canceled.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)