[jira] [Updated] (BEAM-10760) Cleanup timers lead to unbounded state accumulation in global window

["Kenneth Knowles (Jira)" <ji...@apache.org>]

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

Kenneth Knowles updated BEAM-10760:
-----------------------------------
    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.

> Cleanup timers lead to unbounded state accumulation in global window
> --------------------------------------------------------------------
>
>                 Key: BEAM-10760
>                 URL: https://issues.apache.org/jira/browse/BEAM-10760
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-flink
>    Affects Versions: 2.21.0
>            Reporter: Thomas Weise
>            Assignee: Thomas Weise
>            Priority: P2
>             Fix For: 2.25.0
>
>          Time Spent: 6h 20m
>  Remaining Estimate: 0h
>
> For each key, the runner sets a cleanup timer that is designed to garbage collect state at the end of a window. For a global window, these timers will stay around until the pipeline terminates. Depending on the key cardinality, this can lead to unbounded state growth, which in the case of the Flink runner is observable in the growth of checkpoint size.
> https://lists.apache.org/thread.html/rae268806035688b77646195505e5b7a56568a38feb1e52d6341feedd%40%3Cdev.beam.apache.org%3E



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