[jira] [Comment Edited] (IGNITE-9658) Add ability to disable memory deallocation on deactivation.

["Alexei Scherbakov (JIRA)" <ji...@apache.org>]

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

Alexei Scherbakov edited comment on IGNITE-9658 at 9/28/18 5:01 PM:
--------------------------------------------------------------------

[~ivandasch],

Your implementation has memory leak issues.

I've made fixes in separate branch ignite-9658-2, PR [1], TC [2]

If you don't mind I'll finish the ticket.

[1] https://github.com/apache/ignite/pull/4874
[2] https://ci.ignite.apache.org/viewLog.html?buildId=1963526&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll


was (Author: ascherbakov):
[~ivandasch],

Your implementation has memory leak issues.

I've made fixes in separate branch ignite-9658-2, PR [1], TC [2]

If you don't mind I'll finish the ticket.

[1] https://github.com/apache/ignite/pull/4874
[2] https://ci.ignite.apache.org/viewQueued.html?itemId=1963202&tab=queuedBuildOverviewTab

> Add ability to disable memory deallocation on deactivation.
> -----------------------------------------------------------
>
>                 Key: IGNITE-9658
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9658
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Ivan Daschinskiy
>            Assignee: Alexei Scherbakov
>            Priority: Major
>             Fix For: 2.8
>
>
> Currently, in some systems (i.e. RHEL 7.4), we can see, that during massive UNSAFE.freeMemory process freezes. This behaviour can lead to SEGMENTATION of node, especcially when ZookeeperDiscoverySPI is used. There should be an abillity to disable memory deallocation during deactivation of cluster.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)