Most likely node A has some gossip related problems. You can try purging
the gossip state on node A, as per the procedure:
https://docs.datastax.com/en/cassandra/2.1/cassandra/operations/ops_gossip_purge.html
.
Yabin
On Mon, Oct 3, 2016 at 2:38 AM, Girish Kamarthi <
girish.kamar...@stellapps.com>
Hi All,
I want to test out a scenario where there is intermittent network issues on
one of the node.
I've got Cassandra 3.7 cluster of 3 nodes with the keyspace replication
factor of 3.
All the 3 nodes(node A, node B, node C) are started and are in sync. When
one of the cassandra node went down
