[
https://issues.apache.org/jira/browse/CASSANDRA-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751650#comment-13751650
]
Nick Bailey commented on CASSANDRA-5838:
----------------------------------------
So this changes moves all the mbeans into a single domain due to how 3.0 does
things (see attached picture).
This will break all existing clients for the new metrics mbeans (did we update
nodetool and such or are they using the old mbeans?). I'm not really a huge fan
of this change for that reason. From discussion on IRC it looks like we'd need
to have multiple jmx reporters defined to match the old behavior. Or there is
some speculation that this might be fixed/easier in metrics 3.1.
I'd be in favor of reverting this until we can figure out how to match the old
format or confirm the current behavior (breaking) is absolutely what we want
going forward.
> Upgrade metrics-core library
> ----------------------------
>
> Key: CASSANDRA-5838
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5838
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Eugen Paraschiv
> Assignee: Dave Brosius
> Priority: Minor
> Fix For: 2.1
>
> Attachments: 5838-2.txt, 5838-3.txt, 5838.txt, Screen Shot 2013-08-27
> at 2.53.39 PM.png
>
>
> Cassandra is now using [metrics|https://github.com/codahale/metrics] and is
> depending on metrics-core 2.0.3.
> It would be great to make the jump to the latest version of the library which
> is 3.x - [latest is
> 3.0.1|http://search.maven.org/#search|gav|1|g%3A%22com.codahale.metrics%22%20AND%20a%3A%22metrics-core%22].
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
