could it be related to CASSANDRA-9180 <https://issues.apache.org/jira/browse/CASSANDRA-9180> which was fixed in 2.0.15? although it really behaves like CASSANDRA-10231 <https://issues.apache.org/jira/browse/CASSANDRA-10231> which I don’t see any reference to it being in 2.0.x
> On Sep 24, 2015, at 12:57 PM, Robert Coli <rc...@eventbrite.com> wrote: > > On Mon, Sep 14, 2015 at 7:53 PM, K F <kf200...@yahoo.com > <mailto:kf200...@yahoo.com>> wrote: > I have cassandra 2.0.14 deployed and after following the method described in > Apache Cassandra™ 2.0 > <http://docs.datastax.com/en/cassandra/2.0/cassandra/operations/ops_gossip_purge.html> > to clear the gossip state of the node in one of the dc of my cluster > > Why did you need to do this? > > I see wierd exception on the nodes not many but a few in an hour for nodes > that have already successfully decommissioned from the cluster, you can see > from below exception that 10.0.0.1 has been already decommissioned. Below is > the exception snippet. > > Have you done : > > nodetool gossipinfo |grep SCHEMA |sort | uniq -c | sort -n > > and checked for schema agreement... ? > > =Rob > Regards, Ryan Svihla
