[
https://issues.apache.org/jira/browse/CASSANDRA-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726158#action_12726158
]
Jonathan Ellis commented on CASSANDRA-272:
------------------------------------------
Yes, please have a look at DBAS, expose the relevant ones via JMX, and get rid
of the old ganglia stuff.
If we are tracking the same stat in two places though for table/CF we should
just track it in CF and then report the table stat by aggregating the CF ones.
(Even for a few thousand CFs, far more than anyone actually uses at this point,
this is a reasonable approach.)
I also had a note over in CASSANDRA-183 (which I will close in favor of this
one): "DBAS updating in Table is very repetitive, shouldn't that be done in a
single place per op type (ReadCommand / RowMutationCommand) ?"
> Enhance how metrics are exposed
> -------------------------------
>
> Key: CASSANDRA-272
> URL: https://issues.apache.org/jira/browse/CASSANDRA-272
> Project: Cassandra
> Issue Type: New Feature
> Affects Versions: 0.3
> Reporter: Sammy Yu
> Assignee: Sammy Yu
> Priority: Minor
> Fix For: 0.3
>
>
> Had discussion on IRC about the metric interfaces that are used in the code
> today. There are two sets one using IAnalyticsSource to send data to
> Gangalia and another set of interface using JMX MBeans (ie,
> ColumnStoreFamily).
> Since FB is not using Gangalia anymore and it looks like the other
> VMAnalyticsSource is already available via JMX, we should prefer to expose
> metrics through JMX. I will add a new TableMBean which exposes the metrics
> in DBAnalyticsSource.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
