[
https://issues.apache.org/jira/browse/BEAM-6440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744189#comment-16744189
]
Maximilian Michels commented on BEAM-6440:
------------------------------------------
We should consider backporting this to 2.9.0 if we do a hotfix release.
> FlinkTimerInternals memory leak
> -------------------------------
>
> Key: BEAM-6440
> URL: https://issues.apache.org/jira/browse/BEAM-6440
> Project: Beam
> Issue Type: Bug
> Components: runner-flink
> Affects Versions: 2.9.0
> Reporter: Thomas Weise
> Assignee: Maximilian Michels
> Priority: Major
> Fix For: 2.10.0
>
> Attachments: image-2019-01-15-10-31-43-618.png,
> image-2019-01-15-10-41-08-200.png
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> After running a portable streaming app for 2-3 days, we see heap space
> exhausted. Memory analysis shows large number of TimerData objects referenced
> by heap state.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
