ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxim Muzafarov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8469) Non-heap memory leak for calling cluster activation multi times
Date Thu, 08 Nov 2018 11:41:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16679644#comment-16679644

Maxim Muzafarov commented on IGNITE-8469:


If you are checking the 2.7 release branch it seems to me that it's not possible to run a
different cluster on the same PDS files (don't know if this correct). This is was my case.

> 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

This message was sent by Atlassian JIRA

View raw message