cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Smith (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-8433) Add jmx and mdoetool controls to reset lifetime metrics to zero
Date Fri, 05 Dec 2014 20:10:13 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-8433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Donald Smith updated CASSANDRA-8433:
------------------------------------
    Description: 
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.


  was:
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.


> Add jmx and mdoetool 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)

Mime
View raw message