You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Luchnikov Alexander (Jira)" <ji...@apache.org> on 2022/05/13 10:38:00 UTC

[jira] [Updated] (IGNITE-16866) Integer value is out of bounds when the dataregion maxSize is large enough

     [ https://issues.apache.org/jira/browse/IGNITE-16866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luchnikov Alexander updated IGNITE-16866:
-----------------------------------------
    Labels: ise.lts  (was: )

> 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.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.7#820007)