Ignite Cache Details Test
Apache Ignite comes with a feature rich cache with various configurations which can be used as per the requirement of the application using the cache.
This test is an extension of Cache Test and gather metrics around the key features of the cache if they are enabled or not. While debugging the cache this information is key to get to the bottom of the issue for administrators.
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
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. |
Measurement |
Description |
Measurement Unit |
Interpretation |
---|---|---|---|
Is cache empty? |
Indicates if the cache is empty |
Boolean |
|
Is index rebuild in progress? |
Indicates if currently the index rebuild is in progress. |
Boolean |
If the index rebuilt in progress, cache performance may be slow. |
Is cache in read-through mode? |
Indicates if the cache is in read-through mode i.e. application will use cache primarily to read data. |
Boolean |
If the cache is being used in read through mode, it is important for administrators to ensure that cache is completely in sync with database, so as to provide latest data. |
Is management enabled? |
Indicates if the cache management is enabled for the given cache. |
Boolean |
|
Is statistic collection enabled? |
Indicates if the statistics collection is enabled. |
Boolean |
|
Is cache store by value? |
Indicates if cache is configured in store by value mode. |
Boolean |
|
Is cache topology valid for reading? |
Indicates if the cache is configured in a topology provides valid read operations. |
Boolean |
The way cache topology is designed and how cache is distributed across the nodes may affect reading and writing efficiency. |
Is cache topology valid for writing? |
Indicates if the cache is configured in a topology provides valid write operations. |
Boolean |
The way cache topology is designed and how cache is distributed across the nodes may affect reading and writing efficiency. |
Is write behind enabled? |
Indicates if the write behind is enabled and cache data is being synchronized with persistence store. |
Boolean |
Write behind ensures that cache data is written back to database on regular intervals. |
Is cache in write-through mode? |
Indicates if the cache is in write-through mode i.e. application will use cache primarily to write data to persistence store. |
Boolean |
If the cache is being used in write through mode, it is important for administrators to ensure that cache is completely in sync with database, so as to provide latest data to consumers which might be reading from database. |