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 1: Line 1:
=Internal=


=Overview=


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 ''number of entries'' is a read-only Infinispan cache metric representing the current number of cache entries (key/value pairs) maintained by the cache node being interrogated. Note that for distributed or replicated cache, the node may maintain "original" entries and duplicated entries. The value of "number of entries" accounts for ''all'' entries, either original or duplicates, physically present on the node that is being interrogated. The value has no bearing on the total number of distinct entries in the logical cache, which is exposed as "clusterwide number of entries". Unlike the "clusterwide number of entries", the "number of entries" seems to be synchronized across the cluster on each write.
 
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 <tt>[[#clusterwide-number-of-entries|clusterwide-number-of-entries]]</tt>. Unlike <tt>clusterwide-number-of-entries</tt>, <tt>number-of-entries</tt> seems to be synchronized across the cluster on each write.


For configuration details see "[[Infinispan_Cache_Container_Configuration#owners|owners]]".
For configuration details see "[[Infinispan_Cache_Container_Configuration#owners|owners]]".


The metric is also available as the "numberOfEntries" JMX Attribute of the MBean
The metric is also available as the "numberOfEntries" JMX Attribute of the MBean
The number of entries is maintain as an Integer.
May return null if the cache is not started.


<pre>
<pre>
Line 26: Line 31:
where the cluster consists in 1 ... n nodes.
where the cluster consists in 1 ... n nodes.


==clusterwide number of entries==
=Clusterwide Number of Entries=





Revision as of 17:29, 20 October 2016

Internal

Overview

The number of entries is a read-only Infinispan cache metric representing the current number of cache entries (key/value pairs) maintained by the cache node being interrogated. Note that for distributed or replicated cache, the node may maintain "original" entries and duplicated entries. The value of "number of entries" accounts for all entries, either original or duplicates, physically present on the node that is being interrogated. The value has no bearing on the total number of distinct entries in the logical cache, which is exposed as "clusterwide number of entries". Unlike the "clusterwide number of entries", the "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

The number of entries is maintain as an Integer.

May return null if the cache is not started.


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".