[
https://issues.apache.org/jira/browse/IGNITE-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16481997#comment-16481997
]
Maxim Muzafarov commented on IGNITE-8469:
-----------------------------------------
[~dpavlov]
TC ready, Run :: All look good: [#1747 (19 May 18
16:43)|https://ci.ignite.apache.org/viewLog.html?buildId=1313087&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll]
I've also rerun some suspicious suites:
Activate | Deactivate Cluster [#976 (19 May 18
18:04)|https://ci.ignite.apache.org/viewLog.html?buildId=1313106&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_ActivateDeactivateCluster]
Run :: PDS [#1786 (20 May 18
13:19)|https://ci.ignite.apache.org/viewLog.html?buildId=1314160&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAllPds]
Data Structures [#805 (20 May 18
13:38)|https://ci.ignite.apache.org/viewLog.html?buildId=1314206&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_DataStructures]
But I can't get clear build without execution timeouts and snapshot dependency
fails.
> Non-heap memroy 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.6
>
>
> 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)
