Hi André,
That looks like something that I've run into as well on previous
versions of Cassandra. Our workaround was to not drop a keyspace and
the re-use it (which we were doing as part of a test suite).
This is a related stackoverflow post:
http://stackoverflow.com/questions/11623356/cassandra-
Hi, I have an application that will be very dormant most of the time
but will need high-bursting a few days out of the month. Since we are
deploying on EC2 I would like to keep only one Cassandra server up
most of the time and then on burst days I want to bring one more
server up (with more RAM and
