You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "paul cannon (JIRA)" <ji...@apache.org> on 2010/09/28 00:42:33 UTC

[jira] Created: (CASSANDRA-1548) renaming a keyspace, then trying to use original name again makes errorations

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.


[jira] Commented: (CASSANDRA-1548) renaming a keyspace, then trying to use original name again makes errorations

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915745#action_12915745 ] 

Jonathan Ellis commented on CASSANDRA-1548:
-------------------------------------------

+1

> 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
>            Assignee: Gary Dusbabek
>            Priority: Minor
>             Fix For: 0.7.0
>
>         Attachments: test_case_1548.py, v1-0001-ensure-that-a-table-unloads-CFS-instances-when-they-ar.txt
>
>
> 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.


[jira] Updated: (CASSANDRA-1548) renaming a keyspace, then trying to use original name again makes errorations

Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Dusbabek updated CASSANDRA-1548:
-------------------------------------

    Attachment: v1-0001-ensure-that-a-table-unloads-CFS-instances-when-they-ar.txt

> 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
>            Assignee: Gary Dusbabek
>            Priority: Minor
>             Fix For: 0.7.0
>
>         Attachments: test_case_1548.py, v1-0001-ensure-that-a-table-unloads-CFS-instances-when-they-ar.txt
>
>
> 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.


[jira] Commented: (CASSANDRA-1548) renaming a keyspace, then trying to use original name again makes errorations

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916129#action_12916129 ] 

Hudson commented on CASSANDRA-1548:
-----------------------------------

Integrated in Cassandra #550 (See [https://hudson.apache.org/hudson/job/Cassandra/550/])
    ensure that a table unloads CFS instances when they are cleared. patch by gdusbabek, reviewed by jbellis. CASSANDRA-1548


> 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
>            Assignee: Gary Dusbabek
>            Priority: Minor
>             Fix For: 0.7 beta 2
>
>         Attachments: test_case_1548.py, v1-0001-ensure-that-a-table-unloads-CFS-instances-when-they-ar.txt
>
>
> 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.


[jira] Updated: (CASSANDRA-1548) renaming a keyspace, then trying to use original name again makes errorations

Posted by "paul cannon (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

paul cannon updated CASSANDRA-1548:
-----------------------------------

    Attachment: test_case_1548.py

a test case which tickles this bug, using pycassa

> 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
>            Assignee: Gary Dusbabek
>            Priority: Minor
>             Fix For: 0.7.0
>
>         Attachments: test_case_1548.py
>
>
> 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.


[jira] Updated: (CASSANDRA-1548) renaming a keyspace, then trying to use original name again makes errorations

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-1548:
--------------------------------------

         Assignee: Gary Dusbabek
    Fix Version/s: 0.7.0

> 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
>            Assignee: Gary Dusbabek
>            Priority: Minor
>             Fix For: 0.7.0
>
>         Attachments: test_case_1548.py
>
>
> 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.