Cassandra Services Test
Gossip is a peer-to-peer communication protocol in which nodes periodically exchange state information about themselves and about other nodes they know about. The gossip process runs every second and exchanges state messages with up to three other nodes in the cluster. The nodes exchange information about themselves and about the other nodes that they have gossiped about, so all nodes quickly learn about all other nodes in the cluster. A gossip message has a version associated with it, so that during a gossip exchange, older information is overwritten with the most current state for a particular node. Likewise, the native transport is the CQL Native Protocol that is the way all modern Cassandra Driver's communicate with the server. The native protocol defines the format of the binary messages exchanged between the driver and Cassandra over TCP. If these protocol services are not running, then, in large environments, a few of the Cassandra Database nodes may not be up to date. This may cause data inconsistencies in production environments. To avoid such data inconsistencies, it is important to keep a constant vigil on the protocol services and figure out if the protocol services are running at all times! The Cassandra Services test helps administrators in this regard!
This test monitors the Gossip protocol service and the Native protocol service and reports whether the services are running or not. Using this test, administrators can figure out the protocol service that is not running and rectify the same before data mismatch is noticed by the end users!
Target of the test : A Cassandra Database node
Agent deploying the test : An external/remote agent
Outputs of the test : One set of results for the target Cassandra Database node being monitored.
| Parameters | Description |
|---|---|
|
Test Period |
How often should the test be executed. |
|
Host |
The host for which the test is to be configured. |
|
Port |
The port on which the specified host listens. By default, this is 9042. |
|
JMX Remote Port |
Here, specify the port at which the JMX listens for requests from remote hosts. 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 Enabling JMX Support for JRE. |
|
JMX User and JMX Password |
If JMX requires authentication only (but no security), then ensure that the user and 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 Configuring the eG Agent to Support JMX Authentication. |
|
Confirm Password |
Confirm the Password by retyping it in this text box. |
| Measurement | Description | Measurement Unit | Interpretation | ||||||
|---|---|---|---|---|---|---|---|---|---|
|
Is Gossip running? |
Indicates whether/not the Gossip protocol service is running. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate whether/not the protocol service is running. The graph of this measure however, is represented using the numeric equivalents only i.e., 0 or 1. |
||||||
|
Is Native transport running? |
Indicates whether/not the native transport service is running. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate whether/not the transport service is running. The graph of this measure however, is represented using the numeric equivalents only i.e., 0 or 1. |
