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

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on IGNITE-9658:
----------------------------------------

GitHub user ivandasch opened a pull request:

    https://github.com/apache/ignite/pull/4801

    IGNITE-9658 Add ability to skip free initialized memory regions on de…

    …activation.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-9658

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/4801.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4801
    
----
commit 4c6d0433ce8b5ac66d769a9b06491833f1a0ee01
Author: Ivan Daschinskiy <iv...@...>
Date:   2018-09-21T07:38:28Z

    IGNITE-9658 Add ability to skip free initialized memory regions on deactivation.

----


> 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: Ivan Daschinskiy
>            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)