cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9448) Metrics should use up to date nomenclature
Date Fri, 19 Jun 2015 16:21:00 GMT

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

Tyler Hobbs commented on CASSANDRA-9448:
----------------------------------------

bq. Other than nodetool tablestats and tablehistograms are there other way to test the metrics?

Do you mean with an automated test?  In the dtests you can use the jmxutils.py module to make
JMX queries.

> Metrics should use up to date nomenclature
> ------------------------------------------
>
>                 Key: CASSANDRA-9448
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9448
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Sam Tunnicliffe
>            Assignee: Stefania
>              Labels: docs-impacting, jmx
>             Fix For: 3.0 beta 1
>
>
> There are a number of exposed metrics that currently are named using the old nomenclature
of columnfamily and rows (meaning partitions).
> It would be good to audit all metrics and update any names to match what they actually
represent; we should probably do that in a single sweep to avoid a confusing mixture of old
and new terminology. 
> As we'd need to do this in a major release, I've initially set the fixver for 3.0 beta1.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message