Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 5 Dec 2014 20:09:16 +0000 (UTC)
From: "Donald Smith (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12759747.1417804206000.87799.1417810156058@Atlassian.JIRA>
In-Reply-To: <JIRA.12759747.1417804206000@Atlassian.JIRA>
References: <JIRA.12759747.1417804206000@Atlassian.JIRA>
 <JIRA.12759747.1417804206460@arcas>
Subject: [jira] [Updated] (CASSANDRA-8433) Add jmx and mdoetool controls to
 reset lifetime metrics to zero
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Donald Smith updated CASSANDRA-8433:
------------------------------------
    Summary: Add jmx and mdoetool controls to reset lifetime metrics to zero  (was: Add jmx control to reset 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.


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