[
https://issues.apache.org/jira/browse/BEAM-10760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise updated BEAM-10760:
--------------------------------
Description:
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
was: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.
> 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.
> https://lists.apache.org/thread.html/rae268806035688b77646195505e5b7a56568a38feb1e52d6341feedd%40%3Cdev.beam.apache.org%3E
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
