flink-issues mailing list archives

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

     [ https://issues.apache.org/jira/browse/FLINK-10033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Till Rohrmann resolved FLINK-10033.
-----------------------------------
    Resolution: Fixed

Fixed via
master: df22e91b52ca112090d652b7b36f2c647362009b
1.6.0: 06f6a85ca8d29249766819144f571149ad9fcd3d
1.5.3: 41540f12d747331fe87ea0c6cc9d1a2da3279df7

> 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