[
https://issues.apache.org/jira/browse/IGNITE-21219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-21219:
-------------------------------
Description:
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.
was: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.
> 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
> 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)
