Default Parameters for CassCacheTest

This test auto-discovers the caches on the target database server. For each cache discovered, this test reports the maximum cache size and how much of this size is presently occupied by cached data; this reveals, whether/not the cache has enough RAM to hold additional data. Inconsistencies in cache sizing can be detected in the process and their impact on performance analyzed. This test also throws light on how well the cache services requests. Using this test, administrators can figure out the cache from which the least requests have been serviced and analyze the real reason behind such poor responsiveness.

This page depicts the default parameters that need to be configured for the CassCacheTest.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• Specify the port at which the JMX listens for requests from remote hosts in JMX REMOTE PORT text box. Ensure that you specify the same port that you configured in the cassandra-env.sh file (if the target Cassandra Database node is installed on a Unix host) or the cassandra-env.ps1 file (if the target Cassandra Database node is installed on a Windows host) in the (CASSANDRA_HOME) directory used by the target Cassandra Database node. To know how to specify the remote port, refer to Monitoring Cassandra Database document.

• If JMX requires authentication only (but no security), then ensure that the JMX USER and JMX PASSWORD parameters are configured with the credentials of a user with read-write access to JMX. To know how to create this user, refer to Monitoring Cassandra Database document.

• Confirm the JMX PASSWORD by retyping it in the CONFIRM PASSWORD text box.

• Once the necessary values have been provided, clicking on the Update button will register the changes made.

• Once the above value is provided, click on the Update button to register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz” and $port will be changed to “80” when configuring a test.