reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Weimer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1250) Memory leak in Evaluators
Date Tue, 03 May 2016 00:56:12 GMT

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

Markus Weimer commented on REEF-1250:
-------------------------------------

{quote}
How to verify that this is the actual root cause? 
{quote}

That is really tricky. Maybe mock-out the surrounding and test {{Evaluators}} in isolation?

{quote}
And how do we want to fix this (regardless of whether it is)? Is it safe for us to forget
about evaluators which have been returned?
{quote}

Yes, for the most part. We should keep their ID around to throw proper exceptions if they
check in again later. That might happen due to a network partitioning.


> Memory leak in Evaluators
> -------------------------
>
>                 Key: REEF-1250
>                 URL: https://issues.apache.org/jira/browse/REEF-1250
>             Project: REEF
>          Issue Type: Bug
>          Components: REEF Driver
>            Reporter: Markus Weimer
>            Priority: Minor
>
> In {{Evaluators}}, we keep track of all the Evaluators that ever existed. Including the
ones that have failed or been returned. For very long running Drivers, this is a memory leak.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message