Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Duplicate
-
None
-
None
-
None
-
Normal
Description
As part of our continuos delivery pipeline, in some environments we drop and recreate our schema on every build. This occasionally fails with the following error from the client:
com.datastax.driver.core.exceptions.AlreadyExistsException: Keyspace <keyspace-name> already exists
When looking into each node individually after this exception, one node still contains the keyspace and all other nodes no longer show it. After restarting all cassandra nodes, none of them have the keyspace.
We have attached the logs we get from our client and the nodes. We have seen this problem with cassandra 2.0.8 and 2.0.12
Attachments
Attachments
Issue Links
- duplicates
-
CASSANDRA-9424 Schema Improvements
- Open