cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Coli <rc...@eventbrite.com>
Subject Re: Seeing null pointer exception 2.0.14 after purging gossip state
Date Thu, 24 Sep 2015 17:57:20 GMT
On Mon, Sep 14, 2015 at 7:53 PM, K F <kf200467@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

Mime
View raw message