You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Zakelly Lan (Jira)" <ji...@apache.org> on 2024/12/09 03:16:00 UTC

[jira] [Resolved] (FLINK-36859) Wrong epoch/watermark firing in async state processing

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

Zakelly Lan resolved FLINK-36859.
---------------------------------
    Resolution: Fixed

> Wrong epoch/watermark firing in async state processing
> ------------------------------------------------------
>
>                 Key: FLINK-36859
>                 URL: https://issues.apache.org/jira/browse/FLINK-36859
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Task
>            Reporter: Zakelly Lan
>            Assignee: Zakelly Lan
>            Priority: Major
>              Labels: pull-request-available
>
> Currently, we use `EpochManager` to manage the watermark in async state processing. We found an issue when a watermark reached and no further input reach for a while, the epoch/watermark will be triggered twice.



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