[
https://issues.apache.org/jira/browse/CASSANDRA-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425160#comment-13425160
]
Yuki Morishita commented on CASSANDRA-4009:
-------------------------------------------
If we can implement current metrics without breaking interface compatibility,
it is possible to use more types from library. For example, the reason I didn't
use Histogram is that it is impossible to implement current "recent" metrics
whose value is cleared for every access. Some hit ratio have "recent" ones too.
One possible way is we can provide incompatible new metrics using native
Metrics library types while preserving current metrics by measuring twice for
some metrics, but we will not providing "recent" metrics for new system.
> Increase usage of Metrics and flesh out o.a.c.metrics
> -----------------------------------------------------
>
> Key: CASSANDRA-4009
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4009
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Brandon Williams
> Assignee: Yuki Morishita
> Priority: Minor
> Fix For: 1.2
>
> Attachments: 4009.txt, 4009.txt
>
>
> With CASSANDRA-3671 we have begun using the Metrics packages to expose stats
> in a new JMX structure, intended to be more user-friendly (for example, you
> don't need to know what a StorageProxy is or does.) This ticket serves as a
> parent for subtasks to finish fleshing out the rest of the enhanced metrics.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
