cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-1123) Allow tracing query details
Date Mon, 27 Aug 2012 15:18:07 GMT


Jonathan Ellis commented on CASSANDRA-1123:

bq. the JMX one is a descendant of DebuggableTP and that one propagates the trace state which
we wouldn't want when writing the traces themselves

Hmm, can we do something clever like
to just log o.a.c.tracing to stdout + R so we don't just error out silently when something
goes wrong w/ tracing?
> Allow tracing query details
> ---------------------------
>                 Key: CASSANDRA-1123
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: David Alves
>             Fix For: 1.2.0
>         Attachments: 1123-3.patch.gz, 1123.patch, 1123.patch, 1123.patch, 1123.patch
> In the spirit of CASSANDRA-511, it would be useful to tracing on queries to see where
latency is coming from: how long did row cache lookup take?  key search in the index?  merging
the data from the sstables?  etc.
> The main difference vs setting debug logging is that debug logging is too big of a hammer;
by turning on the flood of logging for everyone, you actually distort the information you're
looking for.  This would be something you could set per-query (or more likely per connection).
> We don't need to be as sophisticated as the techniques discussed in the following papers
but they are interesting reading:

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

View raw message