Re: UnknownColumnFamilyException after removing all Cassandra data

The node will not bootstrap if it is listed as a seed node. -- Jacob Shadix On Tue, Feb 7, 2017 at 12:16 PM, Simone Franzini wrote: > To further add to my previous answer, the node in question is a seed node, > so it did not bootstrap. > Should I remove it from the list

Re: UnknownColumnFamilyException after removing all Cassandra data

To further add to my previous answer, the node in question is a seed node, so it did not bootstrap. Should I remove it from the list of seed nodes and then try to restart it? Simone Franzini, PhD http://www.linkedin.com/in/simonefranzini On Tue, Feb 7, 2017 at 9:43 AM, Simone Franzini

Re: UnknownColumnFamilyException after removing all Cassandra data

This is exactly what I did on the second node. If this is not the correct / best procedure to adopt in these cases, please advise: 1. Removed all the data, including the system table (rm -rf data/ commitlog/ saved_caches). 2. Configured the node to replace itself, by adding the following line to

Re: UnknownColumnFamilyException after removing all Cassandra data

The node is trying to communicate with another node, potentially streaming data, and is receiving files/data for an "unknown column family". That is, it doesn't know about the CF with the id e36415b6-95a7-368c-9ac0- ae0ac774863d. If you deleted some columnfamilies but not all the system keyspace

UnknownColumnFamilyException after removing all Cassandra data

I am trying to restore functionality of a cluster that got into a really bad state of schema disagreements. Right now, I am at a point where I have a single node up and I am trying to replicate data from there. I am then trying to bring up a second node, where I deleted all Cassandra data. The