You can check the schema using cassandra-cli, run "describe cluster" it will tell you how many schemas are defined.
I think the best approach when you discover bad schemas is to drain then stop the affected node, remove the Location, Migrations and Schema files in the System data directory, restart and let gossip tell the node whats new. Note this will also remove the nodes initial token, which will be read again from the config file. I've cannot remember hearing about a better solution. The errors are probably http://wiki.apache.org/cassandra/FAQ#jna Hope that helps. ----------------- Aaron Morton Freelance Cassandra Developer @aaronmorton http://www.thelastpickle.com On 9 May 2011, at 22:53, Eric tamme wrote: > On Sun, May 8, 2011 at 7:17 PM, aaron morton <aa...@thelastpickle.com> wrote: >> What version are you on ? >> >> Check the nodetool ring from each node in your cluster to check they have >> the same view. > > > I am running 0.7.3. I checked nodetool ring on all hosts and it all > comes back the same. I had some funky business when i dropped the > keyspace (basically an out of memory error) so I added jna.jar to the > host I was dropping from, which worked ... then the others didnt. So > I went back and added jna.jar all around and all but this host seemed > to pickup the change. I had to drop the keyspace again on this host > that is giving me errors - so it had a mismatched schema for some > period ... and maybe it still does??? > > Any more thoughts? Can I check the schema? Can I "force" a schema > update on the node that is giving me errors?... and What do those > errors mean exactly? > > Thanks again, > Eric
