geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darrel Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (GEODE-1292) Investigate how FreeListManager.defragment handles chunks larger than 2G
Date Mon, 16 May 2016 21:17:12 GMT

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

Darrel Schneider reassigned GEODE-1292:
---------------------------------------

    Assignee: Darrel Schneider

> Investigate how FreeListManager.defragment handles chunks larger than 2G
> ------------------------------------------------------------------------
>
>                 Key: GEODE-1292
>                 URL: https://issues.apache.org/jira/browse/GEODE-1292
>             Project: Geode
>          Issue Type: Bug
>          Components: offheap
>            Reporter: Darrel Schneider
>            Assignee: Darrel Schneider
>
> Currently the initial slabs of off-heap memory are always 2G or less in size.
> But if we have two initial slabs that are contiguous in memory what would prevent defragment
from unifying them together into a single slab of 4G?
> If it does this we are in trouble because the chunkSize is a 32-bit int and will overflow.
>  
> Defragment needs to detect this and just create a chunk of 2G and then start a new one.
Or to prevent it from happening we could just check the incoming slabs and throw away a few
bytes to keep them from being contiguous.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message