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 2020/08/19 15:35:00 UTC

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

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

Kenneth Knowles updated BEAM-10760:
-----------------------------------
    Status: Open  (was: Triage Needed)

> 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-core, runner-flink
>    Affects Versions: 2.21.0
>            Reporter: Thomas Weise
>            Assignee: Thomas Weise
>            Priority: P2
>
> 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.



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