You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Thomas Weise (JIRA)" <ji...@apache.org> on 2019/01/15 18:33:00 UTC

[jira] [Commented] (BEAM-6440) FlinkTimerInternals memory leak

    [ https://issues.apache.org/jira/browse/BEAM-6440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16743285#comment-16743285 ] 

Thomas Weise commented on BEAM-6440:
------------------------------------

!image-2019-01-15-10-31-43-618.png|width=100%!

> FlinkTimerInternals memory leak
> -------------------------------
>
>                 Key: BEAM-6440
>                 URL: https://issues.apache.org/jira/browse/BEAM-6440
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-flink
>    Affects Versions: 2.9.0
>            Reporter: Thomas Weise
>            Assignee: Maximilian Michels
>            Priority: Major
>         Attachments: image-2019-01-15-10-31-43-618.png
>
>
> 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)