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

ASF GitHub Bot logged work on BEAM-6440:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 19/Jan/19 00:08
            Start Date: 19/Jan/19 00:08
    Worklog Time Spent: 10m 
      Work Description: mxm commented on issue #7574: [BEAM-6440] Ensure state 
backend key is set for timer deduplication
URL: https://github.com/apache/beam/pull/7574#issuecomment-455726743
 
 
   Run Python Flink ValidatesRunner
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 187203)
    Time Spent: 3h  (was: 2h 50m)

> 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: 3h
>  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)

Reply via email to