[
https://issues.apache.org/jira/browse/CASSANDRA-8433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238060#comment-14238060
]
Donald Smith commented on CASSANDRA-8433:
-----------------------------------------
Ideally, the output from jmx and nodetool would better document what the fields
mean and what time period they cover. I's unclear whether some of the latencies
refer to coordinator node latency for client requests or local disk latency.
I get the impression that "Mean" latency is lifetime. But how do I know? Look
at the source code? That's something I'd like to reset to zero.
> Add jmx and nodetool controls to reset lifetime metrics to zero
> ---------------------------------------------------------------
>
> Key: CASSANDRA-8433
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8433
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Donald Smith
> Priority: Minor
>
> Often I change some parameter in cassandra, in the OS, or in an external
> component and want to see the effect on cassandra performance. Because some
> the jmx metrics are for the lifetime of the process, it's hard to see the
> effect of changes. It's inconvenient to restart all the nodes. And if you
> restart only some nodes (as I often do) then only those metrics reset to zero.
> The jmx interface should provide a way to reset all lifetime metrics to zero.
> And *nodetool* should invoke that to allow resetting metrics from the
> command line.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
