You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Dmitry Baranov (Jira)" <ji...@apache.org> on 2024/02/05 05:50:00 UTC

[jira] [Assigned] (IGNITE-21219) Write memory leak tests

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

Dmitry Baranov reassigned IGNITE-21219:
---------------------------------------

    Assignee: Dmitry Baranov

> Write memory leak tests
> -----------------------
>
>                 Key: IGNITE-21219
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21219
>             Project: Ignite
>          Issue Type: Improvement
>          Components: compute
>            Reporter: Aleksandr
>            Assignee: Dmitry Baranov
>            Priority: Major
>              Labels: ignite-3
>
> Compute jobs handling logic is getting harder to track every reference we have. It seems like we can easily introduce a memory leak. I wonder if we have some microbenchmarks that prove the absence of memory leak in the compute component.
> Important note: the simulation of leaving and joining the cluster of several nodes (candidates, workers) should be done as well.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)