✅ Terminate node2:
/workspace/ds201-lab09/node2/bin/nodetool stopdaemon
✅ Get the gossip information - check for node1:
Solution
/workspace/ds201-lab09/node1/bin/nodetool gossipinfo
Note: node2's gossip state is still present as the node hasn’t been removed from the cluster; however its heartbeat no longer increases.
✅ Restart node2:
/workspace/ds201-lab09/node2/bin/cassandra
✅ Use nodetool to verify that both nodes are running:
/workspace/ds201-lab09/node1/bin/nodetool status
✅ Get the gossip information again (on either node):
Solution
/workspace/ds201-lab09/node1/bin/nodetool gossipinfo
Observe how the generation value is the same as before for node1, but is now different for node2 after it has restarted. The heartbeat value has also reset for node2.
✅ Start cqlsh to connect to node1:
/workspace/ds201-lab09/node1/bin/cqlsh
✅ Execute the following query on the system.peers table:
SELECT peer, data_center, host_id, rack, release_version, rpc_address, schema_version FROM system.peers;
The system.peers table stores the same gossip data about a node's peers. Check and make sure that the values here are some of the same values you saw from the nodetool gossipinfo command. Note that a node does not store a row of peer data for itself; that can be found in the system.local table.