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

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/05/15 18:02:02 UTC

[jira] [Updated] (BEAM-10691) FlinkRunner: pipeline slows down due to expensive output timestamp queue

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

Kenneth Knowles updated BEAM-10691:
-----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Resolved)

Hello! Due to a bug in our Jira configuration, this issue had status:Resolved but resolution:Unresolved.

I am bulk editing these issues to have resolution:Fixed

If a different resolution is appropriate, please change it. To do this, click the "Resolve" button (you can do this even for closed issues) and set the Resolution field to the right value.

> FlinkRunner: pipeline slows down due to expensive output timestamp queue 
> -------------------------------------------------------------------------
>
>                 Key: BEAM-10691
>                 URL: https://issues.apache.org/jira/browse/BEAM-10691
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-flink
>    Affects Versions: 2.23.0, 2.24.0
>            Reporter: Jan Lukavský
>            Assignee: Jan Lukavský
>            Priority: P1
>             Fix For: 2.25.0
>
>          Time Spent: 7h 10m
>  Remaining Estimate: 0h
>
> Pipeline might stop progressing watermark in certain cases due to timer output timestamp not being released from FlinkTimerInternals#outputTimestampQueue. The pipeline has to be restarted from checkpoint to reload the cache and free watermark hold.



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