[
https://issues.apache.org/jira/browse/IGNITE-9157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16565384#comment-16565384
]
ASF GitHub Bot commented on IGNITE-9157:
----------------------------------------
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4470
IGNITE-9157 Optimize data regions memory usage in tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9157
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4470.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 #4470
----
commit 2cd9ec6a68bc88af93c0f0890f9aa566d8f08c8c
Author: Pavel Kovalenko <jokserfn@...>
Date: 2018-08-01T13:58:30Z
IGNITE-9157 Fixed data region sizes.
commit 0b6f4d0c21b2e76ea708548b0fd4302851369481
Author: Pavel Kovalenko <jokserfn@...>
Date: 2018-08-01T14:10:06Z
IGNITE-9157 Fixed data region sizes.
----
> Optimize memory usage of data regions in tests
> ----------------------------------------------
>
> Key: IGNITE-9157
> URL: https://issues.apache.org/jira/browse/IGNITE-9157
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.6
> Reporter: Pavel Kovalenko
> Assignee: Pavel Kovalenko
> Priority: Major
> Fix For: 2.7
>
>
> If we use persistence in tests and do not explicitly set the max size of a
> data region, by default it will be 20% of available RAM on a host. This can
> lead to memory over-usage and sometimes JVMs, where such tests are running,
> will be killed by Linux OOM killer.
> We should find all tests where data region max size has forgotten and set
> this value explicitly to minimal possible value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
