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/08/13 04:42:17 UTC
[jira] Created: (CASSANDRA-1385) nodetool cfstats does not update
after adding new cfs through API
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
Environment: CentOS 5.2
Trunc
Reporter: Arya Goudarzi
Fix For: 0.7 beta 1
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.
[jira] Updated: (CASSANDRA-1385) nodetool cfstats does not update
after adding new cfs through API
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Dusbabek updated CASSANDRA-1385:
-------------------------------------
Attachment: v3-0001-make-CFS-responsible-for-registering-unregistering-mbe.txt
> 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, v3-0001-make-CFS-responsible-for-registering-unregistering-mbe.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.
[jira] Commented: (CASSANDRA-1385) nodetool cfstats does not update
after adding new cfs through API
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899909#action_12899909 ]
Jonathan Ellis commented on CASSANDRA-1385:
-------------------------------------------
+1 LocalPartitioner approach
> 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.
[jira] Updated: (CASSANDRA-1385) nodetool cfstats does not update
after adding new cfs through API
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Dusbabek updated CASSANDRA-1385:
-------------------------------------
Attachment: (was: v2-0001-make-CFS-responsible-for-registering-unregistering-mbe.txt)
> 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, v3-0001-make-CFS-responsible-for-registering-unregistering-mbe.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.
[jira] Updated: (CASSANDRA-1385) nodetool cfstats does not update
after adding new cfs through API
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-1385:
--------------------------------------
Assignee: Gary Dusbabek
Fix Version/s: 0.7 beta 2
(was: 0.7 beta 1)
Priority: Minor (was: Major)
> 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
>
>
> 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.
[jira] Updated: (CASSANDRA-1385) nodetool cfstats does not update
after adding new cfs through API
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Dusbabek updated CASSANDRA-1385:
-------------------------------------
Attachment: v2-0001-make-CFS-responsible-for-registering-unregistering-mbe.txt
> 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, v2-0001-make-CFS-responsible-for-registering-unregistering-mbe.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.
[jira] Commented: (CASSANDRA-1385) nodetool cfstats does not update
after adding new cfs through API
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899968#action_12899968 ]
Gary Dusbabek commented on CASSANDRA-1385:
------------------------------------------
If 'if' was old code.
I also took the liberty of removing the underscores from member variables.
> 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, v3-0001-make-CFS-responsible-for-registering-unregistering-mbe.txt, v4-0001-make-CFS-responsible-for-registering-unregistering-mbe.txt, v4-0002-remove-underscores-from-CFS-members.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.
[jira] Commented: (CASSANDRA-1385) nodetool cfstats does not update
after adding new cfs through API
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CASSANDRA-1385) nodetool cfstats does not update
after adding new cfs through API
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Dusbabek updated CASSANDRA-1385:
-------------------------------------
Attachment: v4-0001-make-CFS-responsible-for-registering-unregistering-mbe.txt
v4-0002-remove-underscores-from-CFS-members.txt
> 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, v3-0001-make-CFS-responsible-for-registering-unregistering-mbe.txt, v4-0001-make-CFS-responsible-for-registering-unregistering-mbe.txt, v4-0002-remove-underscores-from-CFS-members.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.
[jira] Updated: (CASSANDRA-1385) nodetool cfstats does not update
after adding new cfs through API
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Dusbabek updated CASSANDRA-1385:
-------------------------------------
Attachment: v1-0001-make-CFS-constructor-responsible-for-registering-mbean.txt
> 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.
[jira] Commented: (CASSANDRA-1385) nodetool cfstats does not update
after adding new cfs through API
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899940#action_12899940 ]
Jonathan Ellis commented on CASSANDRA-1385:
-------------------------------------------
are the "if (mbs.isRegistered(nameObj))" checks actually necessary or just old code?
should we take this opportunity to s/ColumnFamilyStores/ColumnFamilies/ (and IndexCFS/IndexColumnFamlies) in the mbean names?
> 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, v3-0001-make-CFS-responsible-for-registering-unregistering-mbe.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.
[jira] Commented: (CASSANDRA-1385) nodetool cfstats does not update
after adding new cfs through API
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901009#action_12901009 ]
Hudson commented on CASSANDRA-1385:
-----------------------------------
Integrated in Cassandra #518 (See [https://hudson.apache.org/hudson/job/Cassandra/518/])
CHANGES.txt for CASSANDRA-1385
remove underscores from CFS members. patch by gdusbabek, reviewed by jbellis. CASSANDRA-1385
make CFS responsible for registering/unregistering mbeans. patch by gdusbabek, reviewed by jbellis. CASSANDRA-1385
> 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, v3-0001-make-CFS-responsible-for-registering-unregistering-mbe.txt, v4-0001-make-CFS-responsible-for-registering-unregistering-mbe.txt, v4-0002-remove-underscores-from-CFS-members.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.
[jira] Commented: (CASSANDRA-1385) nodetool cfstats does not update
after adding new cfs through API
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899969#action_12899969 ]
Jonathan Ellis commented on CASSANDRA-1385:
-------------------------------------------
+1
> 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, v3-0001-make-CFS-responsible-for-registering-unregistering-mbe.txt, v4-0001-make-CFS-responsible-for-registering-unregistering-mbe.txt, v4-0002-remove-underscores-from-CFS-members.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.
[jira] Commented: (CASSANDRA-1385) nodetool cfstats does not update
after adding new cfs through API
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CASSANDRA-1385) nodetool cfstats does not update
after adding new cfs through API
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-1385:
--------------------------------------
Affects Version/s: 0.7 beta 1
> 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
>
>
> 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.