|
Configuration of CassKeySpaceTest
This test auto-discovers the keyspaces in the target Cassandra Database node and for each keyspace, this test reports the count of SSTables and memory tables available. In addition, this test reveals the count of bloom filter false positives on each keyspace and the space utilization of the bloom filters in depth. The test also provides insights into the read and write latency of each keyspace so that administrators can get an idea of the keyspace that is lagging behind in catering the requests.
The default parameters associated with this test are as follows:
-
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.
-
To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.
The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
- The eG manager license should allow the detailed diagnosis capability.
- Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.
|