[jira] [Commented] (IGNITE-13266) PDS (Indexing) fails with 'Exit code 137"

["Ivan Bessonov (Jira)" <ji...@apache.org>]

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

Ivan Bessonov commented on IGNITE-13266:
----------------------------------------

So there are two main problems with the suite.

 

Exit with error code 130 - caused by {{StopNodeOrHaltFailureHandler}} in {{WalRolloverRecordLoggingTest}}.

 

Exit with error code 137 - JVM's excessive memory consumption, caused by rapidly started and stopped threads that allocate a lot of memory in parallel. This causes "malloc" to behave really weird, it wasn't meant to be used this way.

Popular fix found on the internet is to set MALLOC_ARENA_MAX environment variable to some low value like 1, 2 or 4. Tested it with 4 both locally and on TC, looks good. We should consider propagating this setting on all suites, I've seen that at least PDS 4 suffers from the same problem.

In general - the longer the suite, the more chances it has to fail with the same error, purely because of threads count and constant memory allocation.

[https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PdsIndexing&tab=buildTypeStatusDiv&branch_IgniteTests24Java8=pull%2F8051%2Fhead]

> PDS (Indexing) fails with 'Exit code 137"
> -----------------------------------------
>
>                 Key: IGNITE-13266
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13266
>             Project: Ignite
>          Issue Type: Test
>            Reporter: Ivan Bessonov
>            Assignee: Ivan Bessonov
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> [https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PdsIndexing&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeHistoryList]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)