For some reasons we had to drop a keyspace and create it again. After dropping when we are trying to create it again, we are facing an issue that keyspace already exits.
I checked in the schema and tables columnfamilies as well, it is not there. Still it is not allowing us create the new one
Can you try running
nodetool describecluster
on a few of the nodes?
If you see multiple schema versions, then the DROP didn't fully take. To resolve, run a rolling bounce of the cluster or just the nodes which see multiple schema versions.
Thanks @aploetz @divyanshu.imsec_154140 for your answers. This is resolved by rolling bounce followed by full repairs on system keyspaces
sometime gossiping takes time to scatter any metadata across all cluster nodes . Hold-on for 10 - 15 min . keep lag (10 min - 20 min ) between two structural change statements .
If issue not resolved , rolling restart is the guided path .
8 People are following this question.
