[
https://issues.apache.org/jira/browse/IGNITE-16866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Pavlov updated IGNITE-16866:
-----------------------------------
Release Note: Fixed 'Integer value is out of bounds' issue when the
dataregion maxSize is large enough (was: Fixed Integer value is out of bounds
when the dataregion maxSize is large enough.)
> Integer value is out of bounds when the dataregion maxSize is large enough
> --------------------------------------------------------------------------
>
> Key: IGNITE-16866
> URL: https://issues.apache.org/jira/browse/IGNITE-16866
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.12
> Reporter: YuJue Li
> Assignee: YuJue Li
> Priority: Minor
> Labels: ise, ise.lts
> Fix For: 2.14
>
> Attachments:
> 0001-IGNITE-16866-Integer-value-is-out-of-bounds-when-the.patch,
> 2022-04-17_09-12.png, IgniteServer.java
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> In the Random2LruPageEvictionTracker and RandomLruPageEvictionTracker,
> trackingSize is int, Therefore, when the maxSize of the dataregion is large
> enough (for example, more than 1.2T), execute GridUnsafe.allocateMemory to
> allocate memory, the maximum value of int will be exceeded.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
