You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Arya Goudarzi (JIRA)" <ji...@apache.org> on 2010/07/29 21:01:37 UTC
[jira] Created: (CASSANDRA-1334) cfstats shows deleted cfs
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
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.
[jira] Updated: (CASSANDRA-1334) cfstats shows deleted cfs
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ 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.0
(was: 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.0
>
>
> 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.
[jira] Commented: (CASSANDRA-1334) cfstats shows deleted cfs
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895247#action_12895247 ]
Hudson commented on CASSANDRA-1334:
-----------------------------------
Integrated in Cassandra #509 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/509/])
unregister CF mbean when a CF is dropped. patch by gdusbabek, reviewed by jbellis. CASSANDRA-1334
> 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
>
> Attachments: 0001-unregiter-CF-mbeans-when-a-CF-is-dropped.patch
>
>
> 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.
[jira] Updated: (CASSANDRA-1334) cfstats shows deleted cfs
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (CASSANDRA-1334) cfstats shows deleted cfs
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis reassigned CASSANDRA-1334:
-----------------------------------------
Assignee: Gary Dusbabek
> 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.
[jira] Commented: (CASSANDRA-1334) cfstats shows deleted cfs
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895011#action_12895011 ]
Jonathan Ellis commented on CASSANDRA-1334:
-------------------------------------------
should we add a CFS.getMBeanName to remove the potential for that code getting out of sync w/ the register?
+1 otherwise
> 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
>
> Attachments: 0001-unregiter-CF-mbeans-when-a-CF-is-dropped.patch
>
>
> 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.
[jira] Updated: (CASSANDRA-1334) cfstats shows deleted cfs
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Dusbabek updated CASSANDRA-1334:
-------------------------------------
Attachment: 0001-unregiter-CF-mbeans-when-a-CF-is-dropped.patch
> 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
>
> Attachments: 0001-unregiter-CF-mbeans-when-a-CF-is-dropped.patch
>
>
> 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.
[jira] Commented: (CASSANDRA-1334) cfstats shows deleted cfs
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895016#action_12895016 ]
Gary Dusbabek commented on CASSANDRA-1334:
------------------------------------------
yeah. that makes good sense. I'll put it in when I commit.
> 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
>
> Attachments: 0001-unregiter-CF-mbeans-when-a-CF-is-dropped.patch
>
>
> 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.