You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2010/07/29 21:09:17 UTC

[jira] Updated: (CASSANDRA-1334) cfstats shows deleted cfs

     [ https://issues.apache.org/jira/browse/CASSANDRA-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-1334:
--------------------------------------

    Fix Version/s: 0.7 beta 1

> cfstats shows deleted cfs
> -------------------------
>
>                 Key: CASSANDRA-1334
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1334
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.7 beta 1
>         Environment: CentOS 5.2
> trunk
>            Reporter: Arya Goudarzi
>            Assignee: Gary Dusbabek
>             Fix For: 0.7 beta 1
>
>
> cfstats shows deleted CFs inside the keyspace after the CF was deleted from the keyspace using thrift service call system_drop_column_family
> Steps to Reproduce:
> 1. Setup a 3 node cluster with clean slate from trunc;
> 2. create a keyspace with rf=2 and a standard cf using service call system_add_keyspace
> 3. create another cf with system_add_column_family
> 4. batch_mutate some rows into the new column family you created in step 3
> 5. call describe_keyspace to get a list of cfs inside your KS
> 6. iterate through the result and call system_drop_column_family for each
> 7. look at cfstats result. it is still showing the very first cf we create in step 2 in the list

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