[
https://issues.apache.org/jira/browse/IGNITE-9658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16627697#comment-16627697
]
Ignite TC Bot commented on IGNITE-9658:
---------------------------------------
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET{color} [[tests
6|https://ci.ignite.apache.org/viewLog.html?buildId=1933202]]
* exe: CancellationTest.TestTask - 0,0% fails in last 100 master runs.
{color:#d04437}PDS (Direct IO) 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1939050]]
* IgnitePdsNativeIoTestSuite:
IgnitePdsCacheConfigurationFileConsistencyCheckTest.testCorruptedCacheConfigurationsValidation
- 0,0% fails in last 100 master runs.
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=1933256&buildTypeId=IgniteTests24Java8_RunAll]
> 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)
