Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-8916

com.datastax.driver.core.exceptions.AlreadyExistsException: Keyspace <keysapce-name> already exists

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

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

        1. client.log
          11 kB
          Joseph Samuel
        2. system.log.1.node1a
          407 kB
          Joseph Samuel
        3. system.log.1.node1b
          423 kB
          Joseph Samuel
        4. system.log.1.node2a
          443 kB
          Joseph Samuel
        5. system.log.1.node2b
          417 kB
          Joseph Samuel

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned Assign to me
            yoseph.samuel@gmail.com Joseph Samuel
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment