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/08/18 18:30:18 UTC

[jira] Commented: (CASSANDRA-1385) nodetool cfstats does not update after adding new cfs through API

    [ https://issues.apache.org/jira/browse/CASSANDRA-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899896#action_12899896 ] 

Jonathan Ellis commented on CASSANDRA-1385:
-------------------------------------------

do we want the "hidden" index CFSes exposed as mbeans?  if we do we probably want them in a different place in the jmx heirarchy to avoid confusion.

> nodetool cfstats does not update after adding new cfs through API
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-1385
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1385
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7 beta 1
>         Environment: CentOS 5.2
> Trunc
>            Reporter: Arya Goudarzi
>            Assignee: Gary Dusbabek
>            Priority: Minor
>             Fix For: 0.7 beta 2
>
>         Attachments: v1-0001-make-CFS-constructor-responsible-for-registering-mbean.txt
>
>
> Start a 3 node cluster. Add a new Keyspace with API. Then add more CFs to that Keyspace. ndoetool cfstats will only show you the CF which was originally part of KsDef creation and not the CfDefs that were added later.

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