This is possible if some of the nodes are available in system peer table of the
other cluster.this usually occurs when we decommission nodes from one cluster
and add to another cluster.also make sure that before adding a node newly to a
cluster all data in drives are properly wiped out .
Sent
Maheshwari <abhishek.maheshw...@timesinternet.in>
Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Date: Wednesday, December 14, 2016 at 3:10 AM
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Subject: Cassandra Different cluster gossip
Hi All,
I am getting below log in my system.log
GossipDigestSynVerbHandler.java:52 - ClusterName mismatch from /192.XXX.AA.133
QA Columbia Cluster! = QA Columbia Cluster new
192.XXX.AA.133 Cluster name is QA Columbia Cluster
And on which server I am getting this error cluster name is: QA
