That behavior went away with 2.2. https://issues.apache.org/jira/browse/CASSANDRA-11752 adds decay to it to make it recent data which is much better then just reseting on reads.
Chris On Tue, Oct 25, 2016 at 2:06 PM, Andrew Bialecki < andrew.biale...@klaviyo.com> wrote: > We're running 3.6. Running "nodetool proxyhistograms" twice, we're seeing > the same data returned each time, but expecting the second run to be reset. > We're seeing the same behavior with "nodetool cfhistograms." > > I believe resetting after each call used to be the behavior, did that > change in recent version? We've confirmed metrics reset after the service > is restarted. > > -- > AB >
