reef-dev mailing list archives

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


Markus Weimer commented on REEF-1250:

How to verify that this is the actual root cause? 

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

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?

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:
>             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

View raw message