[
https://issues.apache.org/jira/browse/BEAM-8212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174650#comment-17174650
]
Beam JIRA Bot commented on BEAM-8212:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> StatefulParDoFn creates GC timers for every record
> ---------------------------------------------------
>
> Key: BEAM-8212
> URL: https://issues.apache.org/jira/browse/BEAM-8212
> Project: Beam
> Issue Type: Bug
> Components: runner-core
> Reporter: Akshay Iyangar
> Priority: P2
> Labels: stale-P2
>
> Hi
> So currently the StatefulParDoFn create timers for all the records.
> [https://github.com/apache/beam/blob/master/runners/core-java/src/main/java/org/apache/beam/runners/core/StatefulDoFnRunner.java#L211]
> This becomes a problem if you are using GlobalWindows for streaming where
> these timers get created and never get closed since the window will never
> close.
> This is a problem especially if your memory bound in rocksDB where these
> timers take up potential space and sloe the pipelines considerably.
> Was wondering that if the pipeline runs in global windows we should avoid
> adding timers to it at all?
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
