cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "paul cannon (JIRA)" <j...@apache.org>
Subject [jira] Created: (CASSANDRA-1548) renaming a keyspace, then trying to use original name again makes errorations
Date Mon, 27 Sep 2010 22:42:33 GMT
renaming a keyspace, then trying to use original name again makes errorations
-----------------------------------------------------------------------------

                 Key: CASSANDRA-1548
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1548
             Project: Cassandra
          Issue Type: Bug
          Components: Core
    Affects Versions: 0.7 beta 2
         Environment: encountered on Debian squeeze, with cassandra from HEAD (r1001931).
 effects can be seen with both Telephus and Pycassa as clients; probably any.
            Reporter: paul cannon
            Priority: Minor


My test case does the following:

* Create a keyspace with at least one CF in it.
* Rename that keyspace
* Create a new keyspace with the same original name, containing a CF with the same name as
earlier.

The second keyspace creation receives an error (although the keyspace does get created):

{{javax.management.InstanceAlreadyExistsException: org.apache.cassandra.db:type=ColumnFamilies,keyspace=keyspacename,columnfamily=cfname}}

After that point, trying to do almost anything with the new keyspace will generate the same
error- even trying to drop it. This persists until cassandra itself is restarted.

One supposes that some JMX thing is lacking reregistration upon keyspace rename.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message