Ignite Cache Groups Test

Caches within a single cache group share various internal structures such as partitions maps, thus boosting topology events processing and decreasing overall memory usage. Note that from the API standpoint, there is no difference whether a cache is a part of a group or not.

Cache groups help in managing the overheads and if there are very large number of caches, the overall time required in deploying and managing the caches will be significantly reduced if using cache groups.

Since the data partitioning is done at cache group level, proper grouping and partitioning within the group is essential to better cache performance. That's the reason it is important to monitor the cache groups, so that any issues can be addressed in timely manner and application performance is not impacted.

This test monitors the cache groups and gathers key statistics around the usage of cache groups and partitions which can help administrators spot any current or future issues and take corrective actions.

Target of the test : Apache Ignite Server

Agent deploying the test : An internal or external agent

Outputs of the test : One set of results for each Apache Ignite Server

Configurable parameters for the test
Parameter	Description
Test period	How often should the test be executed.
Host	Enter the IP address of the Apache Ignite cluster.
Port	Enter the port number on which JMX connector listens to incoming connections requests.
JMX Remote Port	In this text box, enter the name of a virtual warehouse that needs to be monitored. The JMX connector listens on 8686 by default. If it listens on different port in your environment then specify the same.
JMX User	Specify the credentials of the user who is authorized to use JMX.
JMX Password	Specify the password for the authorized user.
Confirm Password	Confirm the password by retyping it here.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Partition for cache group	Indicates the total number of partitions in cache group.	Number	The number of partitions should be optimal based on the performance required and data to be accessed.
Cluster moving partition count	Indicates the total number of partitions for given cache group in the entire cluster with state MOVING.	Number
Cluster owning partition count	Indicates the total number of partitions for given cache group in the entire cluster with state OWNING.	Number
Index build count partition left	Indicates the maximum number of partition copies for all partitions of this cache group.	Number
Local node moving partition	Indicates the count of nodes with MOVING state for given cache group located on a given node.	Number
Local node owning partition	Indicates the count of nodes with OWNING state for given cache group located on a given node.	Number
Local node renting entries	Indicates the number of entries which remains to evict RENTING partitions located on same node for given cache group.	Number
Local node renting partition	Indicates the count of nodes with RENTING state for given cache group located on a given node.	Number
Maximum number of partition copies	Indicates the maximum number of partition copies for all partitions of this partition group.	Number	A very large number of copies can occupy a lot of storage unnecessarily.
Minimum number of partition copies	Indicates the minimum number of partition copies for all partitions of this partition group.	Number	There should be a minimum number of copies to be held in case if there is failure.
Sparsity storage size	Indicates the storage space allocated for the cache group adjusted for sparsity.	MB
Storage size allocated	Indicates the storage space allocated for entire cache group.	MB	Storage allocated should be as per requirement and administrators need to keep an eye on required and used storage so as to use storage optimally.
Cache group total allocated pages	Indicates the total number of memory pages allocated for given cache group.	Number
Cache group total allocated size	Indicates the total size of memory allocated for given cache group.	MB