cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-144) make jmx count/latency stuff actually useful
Date Wed, 06 May 2009 21:37:30 GMT


Jonathan Ellis updated CASSANDRA-144:

    Attachment: 144.patch

> make jmx count/latency stuff actually useful
> --------------------------------------------
>                 Key: CASSANDRA-144
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>         Attachments: 144.patch
> i just track those since "the beginning of time" it is not very useful for monitoring.
> (say things are fine for days, then something breaks -- you have to overcome the days
of fine-ness in the avg before you can see anything wrong.)
> option 1: reset the counters after each request for data.  problem: then i can't have
multiple collectors (which i don't need atm but might be nice to have).
> option 2: keep the last N data points and compute an average on demand, but that's more
complicated than just doing a += for each op.
> going to go with option 2.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message