geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jens Deppe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GEODE-751) RegionMXBean shouldn't rely on Eviction Algorithm for getEntrySize
Date Thu, 07 Jan 2016 20:51:39 GMT

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

Jens Deppe updated GEODE-751:
-----------------------------
    Affects Version/s: 1.0.0-incubating

> RegionMXBean shouldn't rely on Eviction Algorithm for getEntrySize
> ------------------------------------------------------------------
>
>                 Key: GEODE-751
>                 URL: https://issues.apache.org/jira/browse/GEODE-751
>             Project: Geode
>          Issue Type: Improvement
>          Components: management
>    Affects Versions: 1.0.0-incubating
>            Reporter: Jens Deppe
>
> We have the following in the javadoc for method {{getEntrySize}} on interface {{RegionMXBean}}:
> {quote}
> Returns the aggregate entry size (in bytes) of all entries. This will provide a correct
value only if the eviction algorithm has been set to {{EvictionAlgorithm.LRU_MEMORY}}. For
all partition regions it will show entry size in bytes. It will also include size of all the
secondary entries in the data store. So while referring to size one should take redundancy
into account.
> {quote}
> The region memory consumption and the eviction algorithm are two separate concepts, we
should not obligate customers to use a custom eviction algorithm to report the correct memory
consumption for a region. 
> We rely on this attribute to show information on PULSE, so neither the member memory
usage nor cluster memory usage are accurate if the eviction algorithm is not configured as
{{EvictionAlgorithm.LRU_MEMORY}}. 
> To reproduce, start up a cluster with a simple replicated region and insert some data.
You can check afterwards (from JConsole) that the attribute "EntrySize" for the replicated
region is set as "-1".
> We rely on this attribute to show information on PULSE, so neither the member memory
usage nor cluster memory usage are accurate if the eviction algorithm is not configured as
{{EvictionAlgorithm.LRU_MEMORY}}. 



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

Mime
View raw message