[
https://issues.apache.org/jira/browse/IGNITE-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676922#comment-16676922
]
Max Shonichev edited comment on IGNITE-8469 at 11/6/18 3:58 PM:
----------------------------------------------------------------
[~Mmuzaf] what is exact reproducer for that issue? I'm executing 100 iterations
of activate-deactivate and see small increase in total pages sum per process
for both fixed and original version
I'm using
{noformat}
pmap -x | grep 'Total' | awk '{print $3}'
{noformat}
to detect whole memory allocated for apache ignite process
was (Author: mshonichev):
[~Mmuzaf] what is exact reproducer for that issue? I'm executing 100 iterations
of activate-deactivate and see small increase in total pages sum per process
for both fixed and original version
> Non-heap memory leak for calling cluster activation multi times
> ---------------------------------------------------------------
>
> Key: IGNITE-8469
> URL: https://issues.apache.org/jira/browse/IGNITE-8469
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Reporter: Maxim Muzafarov
> Assignee: Maxim Muzafarov
> Priority: Major
> Fix For: 2.7
>
>
> Calling multiple time cluster (with enabled persistence and started client
> nodes) activation {{ig3CB.cluster().active(true);}} leads to non-heap memory
> leak.
> Line
> {{org/apache/ignite/internal/pagemem/impl/PageMemoryNoStoreImpl.java:234}}
> looks suspicious because of in case method
> {{org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl#start}}
> callled multi times (e.g. activate(true) called multi times) we lost info
> about allocated regions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
