[
https://issues.apache.org/jira/browse/IGNITE-12439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014947#comment-17014947
]
Ignite TC Bot commented on IGNITE-12439:
----------------------------------------
{panel:title=Branch: [pull/7210/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4912783&buildTypeId=IgniteTests24Java8_RunAll]
> More descriptive message in situation of IgniteOutOfMemoryException, warning
> message if risk of IOOME is found
> --------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-12439
> URL: https://issues.apache.org/jira/browse/IGNITE-12439
> Project: Ignite
> Issue Type: Improvement
> Reporter: Sergey Chugunov
> Assignee: Sergey Chugunov
> Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In persistent mode starting many caches in a data region of a small size may
> lead to IgniteOutOfMemoryException being thrown.
> The root cause is that each partition requires allocation of one or more
> metapages that should be stored during checkpoint and cannot be replaced by
> other types of pages.
> As a result when too many metapages occupy significant portion of data
> region's space a request to replace a page in memory (with one on disk) may
> not be able to find clean page for replacement. In this situation
> IgniteOutOfMemoryException is thrown.
> It is not easy to prevent IOOME in general case, but we should provide more
> descriptive message when the exception is thrown and/or print out warning to
> logs when too many caches (or one cache with huge number of partitions) are
> started in the same data region.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
