Hi,
We're running a cluster of cassandra 1.1.4 (that was initially started as a 1.0.x cluster) that has a keyspace, OpsCode, from when we first started using DSE (but had to switch to apache cassandra for features in 1.1.x that we needed).
In trying to track down another issue, I'm noticing that we have an old keyspace, OpsCode, that I can't access or drop.
While it's "probably" harmless to leave around, I'd rather clean it up, but am not sure how to do this safely -- the only guess I'd venture is to shut down the cluster, remove the keyspace's directory, and restart it -- but no idea if this is sane at all.
Suggestions?
cqlsh> select * from system.schema_keyspaces;
keyspace | durable_writes | name | strategy_class | strategy_options
-----------+----------------+-----------+------------------------------------------------------+----------------------------
OpsCenter | True | OpsCenter | org.apache.cassandra.locator.SimpleStrategy | {"replication_factor":"2"}
...
cqlsh> use OpsCenter;
Bad Request: Keyspace 'opscenter' does not exist
cqlsh> drop keyspace OpsCenter;
Bad Request: org.apache.cassandra.config.ConfigurationException: Cannot drop non existing keyspace 'opscenter'.
ls -l data/OpsCenter/
total 32
drwxr-xr-x 3 app app 4096 2012-12-20 06:41 events
drwxr-xr-x 3 app app 4096 2012-12-20 06:41 events_timeline
drwxr-xr-x 2 app app 4096 2012-10-29 00:24 pdps
drwxr-xr-x 2 app app 4096 2012-10-29 00:24 rollups300
drwxr-xr-x 2 app app 4096 2012-10-29 00:24 rollups60
drwxr-xr-x 2 app app 4096 2012-10-29 00:24 rollups7200
drwxr-xr-x 2 app app 4096 2012-10-29 00:24 rollups86400
drwxr-xr-x 2 app app 4096 2012-10-29 00:24 settings
