flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-10033) Let Task release reference to Invokable on shutdown
Date Fri, 03 Aug 2018 02:23:00 GMT

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

ASF GitHub Bot commented on FLINK-10033:
----------------------------------------

TisonKun commented on issue #6480: [FLINK-10033] [runtime] Task releases reference to AbstractInvokable
URL: https://github.com/apache/flink/pull/6480#issuecomment-410124471
 
 
   nice catch! memory leaks is one of the most terrible issues, this is helpful. +1 for merge

----------------------------------------------------------------
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:
users@infra.apache.org


> Let Task release reference to Invokable on shutdown
> ---------------------------------------------------
>
>                 Key: FLINK-10033
>                 URL: https://issues.apache.org/jira/browse/FLINK-10033
>             Project: Flink
>          Issue Type: Bug
>          Components: TaskManager
>    Affects Versions: 1.5.2
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.5.3, 1.6.0
>
>
> References to Task objects may under some conditions linger longer than for the lifetime
of the task. For example, in case of local network channels, the receiving task may have a
reference to the object of the task that produced the data.
> To prevent against memory leaks, the Task needs to release all references to its AbstractInvokable
when it shuts down or cancels.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message