cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3671) provide JMX counters for unavailables/timeouts for reads and writes
Date Mon, 27 Feb 2012 18:20:50 GMT


Brandon Williams commented on CASSANDRA-3671:

bq. It does create a split-world syndrome of "new style" vs. "old style" metrics though. I'd
love input.

I'm +1 on this approach, because we need to keep things backwards-compatible for existing
monitoring solutions, but ultimately I'm unhappy with the current state of JMX and starting
fresh like you have here is a good way to solve it.  Fleshing out o.a.c.metrics looks like
the future to me.
> provide JMX counters for unavailables/timeouts for reads and writes
> -------------------------------------------------------------------
>                 Key: CASSANDRA-3671
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Peter Schuller
>            Assignee: Peter Schuller
>            Priority: Minor
>             Fix For: 1.2
>         Attachments: CASSANDRA-3671-trunk-coda-metrics-v1.txt, CASSANDRA-3671-trunk-coda-metrics-v2.txt,
CASSANDRA-3671-trunk-v2.txt, CASSANDRA-3671-trunk.txt
> Attaching patch against trunk.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message