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 f
Maheshwari
Reply-To: "user@cassandra.apache.org"
Date: Wednesday, December 14, 2016 at 3:10 AM
To: "user@cassandra.apache.org"
Subject: Cassandra Different cluster gossiping to each other
Hi All,
I am getting below log in my system.log
GossipDigestSynVerbHandler.j
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 Colum
Did you clear the LocationInfo from the non prod cluster ?
When you gave prod seeds from non-prod, non-prod would have discovered all the
nodes in prod. Unless you have cleared the location info they will still have
that knowledge.
Does nodetool ring in non-prod list any prod machines ?
if
Symptom is that when we populate data into the non-prod cluster, after a while,
we start seeing this warning message from the prod cluster:
"WARN [GossipStage:1] 2011-08-19 19:47:35,730 GossipDigestSynVerbHandler.java
(line 63) ClusterName mismatch from non-prod-node-ip
non-prod-Cluster!=prod-C
