[jira] [Assigned] (GEODE-751) RegionMXBean shouldn't rely on Eviction Algorithm for getEntrySize

["Aaron Lindsey (Jira)" <ji...@apache.org>]

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

Aaron Lindsey reassigned GEODE-751:
-----------------------------------

    Assignee: Jens Deppe

We intent to de-couple the need for eviction information to exist in order to get a measurement on the amount of bytes in a replicate region when we get to this measurement in Micrometer. Can we create a new Jira ticket for fixing this in Micrometer?

> 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: jmx, statistics
>    Affects Versions: 1.0.0-incubating
>            Reporter: Jens Deppe
>            Assignee: Jens Deppe
>            Priority: Major
>
> 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".



--
This message was sent by Atlassian Jira
(v8.3.2#803003)