You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Joseph Samuel (JIRA)" <ji...@apache.org> on 2015/03/05 12:20:38 UTC
[jira] [Created] (CASSANDRA-8916)
com.datastax.driver.core.exceptions.AlreadyExistsException: Keyspace
already exists
Joseph Samuel created CASSANDRA-8916:
----------------------------------------
Summary: com.datastax.driver.core.exceptions.AlreadyExistsException: Keyspace <keysapce-name> already exists
Key: CASSANDRA-8916
URL: https://issues.apache.org/jira/browse/CASSANDRA-8916
Project: Cassandra
Issue Type: Bug
Components: Core
Reporter: Joseph Samuel
Attachments: client.log, system.log.1.node1a, system.log.1.node1b, system.log.1.node2a, system.log.1.node2b
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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)