[
https://issues.apache.org/jira/browse/IGNITE-12042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900773#comment-16900773
]
Pavel Pereslegin commented on IGNITE-12042:
-------------------------------------------
Hello [~slava.koptilin].
Thank you - now this test is falling for me too.
Can we perform this check (ensureFreeSpaceForInsert) *only* when we
*allocating* a new page in free list (AbstractFreeList#allocateDataPage)? Will
it be more "accurate"?
We can throw OOME in "allocateDataPage" and handle it (re-throw) in RowStore
with failure handler.
AFAIK {{ensureFreeSpace}} cannot be performed in such a way because of
deadlocks but this check can.
> Atempt to remove entries from fully populated data region may result in
> IgineOutOfMemoryException
> -------------------------------------------------------------------------------------------------
>
> Key: IGNITE-12042
> URL: https://issues.apache.org/jira/browse/IGNITE-12042
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.7
> Reporter: Vyacheslav Koptilin
> Assignee: Vyacheslav Koptilin
> Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Removing entries from non-persistent data region may require allocating a new
> data page in order to move a tracked page from one bucket of the free-list to
> another one.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
