Configuration of CassMsgTest

This test auto-discovers the nodes that are joining the target Cassandra database node in a cluster and for each node, this test reports the rate at which large messages, small messages and gossip messages were transferred from the target database node. In addition, this test also reveals the rate at which large/small/gossip messages were pending transfer to the joining node and were dropped during transfer. This test also reveals how many messages timed out during transfer. Using this test, administrators can figure out the joining node that is not up to date with the target database nose.

The default parameters associated with this test are as follows:

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

• Specify the IP address of the host for which the test is being configured.

• Specify the PORT at which the HOST listens. The default value is 9042.

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

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.