You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Nigel LEACH <ni...@uk.bnpparibas.com> on 2014/01/21 13:29:17 UTC

Cassandra Complete Initialisation

I have a crash and burn cluster, used for all sorts of integration testing (DataStax 2.0.2, five nodes, 8GB heap, two seeds, vnodes, RF 2). I wanted to completely initialise/refresh my environment, so did something like this (can't be sure something else did not slip in too),

*Removed all user keyspaces 
*Standard shutdown of Cassandra on all nodes
*Deleted all files in saved_caches_directory, data_file_directories, commitlog_directory
*Rebooted all five nodes

Now, I can usually start Cassandra on the first seed, but not anywhere else. There are various errors, but the first, and most prevalent, seem to be 

Loading persisted ring state
ERROR 09:55:36,660 Exception encountered during startup
java.lang.ExceptionInInitializerError
...
Caused by: java.lang.NullPointerException
...
java.lang.ExceptionInInitializerError
...
Exception encountered during startup: null
ERROR 09:55:36,675 Exception in thread Thread[StorageServiceShutdownHook,5,main]
java.lang.ExceptionInInitializerError

Any idea how to get my zapped cluster back up again, and in future how best to fully initialise a Cluster.

I don't want any data, or settings, form the original cluster, although the more settings I can keep, the better, just from the perspective of work involved to creat a clean environmnet.

Many Thanks
Nigel



___________________________________________________________
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is prohibited.

Please refer to http://www.bnpparibas.co.uk/en/email-disclaimer/ for additional disclosures.