cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Dusbabek (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1385) nodetool cfstats does not update after adding new cfs through API
Date Wed, 18 Aug 2010 16:47:16 GMT

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

Gary Dusbabek commented on CASSANDRA-1385:
------------------------------------------

They weren't previously, but I think it makes good sense to expose them.  It would be easy
to segregate them by mbean name if we assume that any CFS with a LocalPartitioner is an internal
and should be grouped in "org.apache.cassandra.db:type=InternalCFS" or something like that.
 The other (more ugly) approach would be to use a flag to indicate hidden/internal CFSs.

> 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.


Mime
View raw message