incubator-directmemory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raffaele P. Guidi (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DIRECTMEMORY-17) Element Eviction/Expiry issue
Date Tue, 18 Oct 2011 19:45:10 GMT

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

Raffaele P. Guidi resolved DIRECTMEMORY-17.
-------------------------------------------

    Resolution: Fixed
      Assignee: Raffaele P. Guidi

created a basic isShortage function. It is configured setting OffHeapMemoryBuffer.maxAllocationErrors
to de desired value - default is zero, meaning that after an allocation error the eviction
starts - if some room is made or the buffer is cleared allacationErrors gets reset
                
> Element Eviction/Expiry issue
> -----------------------------
>
>                 Key: DIRECTMEMORY-17
>                 URL: https://issues.apache.org/jira/browse/DIRECTMEMORY-17
>             Project: Apache DirectMemory
>          Issue Type: Bug
>            Reporter: Ashish Paliwal
>            Assignee: Raffaele P. Guidi
>
> Element eviction (LFU) is happening during normal cleanup task. It would be good to evict
elements only during resource constraint like limited space.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message