Infinispan Cache Number of Entries: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
No edit summary
Line 25: Line 25:


where the cluster consists in 1 ... n nodes.
where the cluster consists in 1 ... n nodes.
==clusterwide number of entries==





Revision as of 17:21, 20 October 2016


A read-only int represents the current number of raw entries maintained in the cache node being interrogated. May return null if the cache is not started.

The exact semantics of the "number-of-entries" for a distributed cache is: the raw number of entries (key/value pairs), either original or duplicates, physically present on that specific node that is being interrogated via the CLI command. The value has not bearing on the total number of distinct entries in the logical cache. For that, see clusterwide-number-of-entries. Unlike clusterwide-number-of-entries, number-of-entries seems to be synchronized across the cluster on each write.

For configuration details see "owners".

The metric is also available as the "numberOfEntries" JMX Attribute of the MBean

jboss.infinispan:type=Cache,name="<cache-name>(dist_sync)",manager="clustered",component=Statistics


Relationship Between clusterwide-number-of-entries and number-of-entries

For a distributed cache, this relationship holds true (provided that clusterwide-number-of-entries is correctly syncrhonized across the cluster and it has an updated value):


number-of-entries[1] + number-of-entries[2] + .. number-of-entries[n] = clusterwide-number-of-entries * owners
                            

where the cluster consists in 1 ... n nodes.

clusterwide number of entries

A read-only int representing the cluster-wide number of distinct entries in the logical cache maintained by the cluster being interrogated. May return null if the cache is not started. The metrics is different than number-of-entries metric.

There are cases cases where clusterwide-number-of-entries is 0 for a non-zero number of keys, and owners=2. In general, it seems it is not continuously updated under load. The metric seems to "catch up" as more keys are added..

For configuration details see "owners".