cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Haddad (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6226) Slow query log
Date Fri, 17 Oct 2014 15:46:34 GMT


Jon Haddad commented on CASSANDRA-6226:

I agree that a slow query log would be very useful.  As an operator, tracing is just a guess.
 What I personally need is a log where I can say "slow_query_time = 3s".  Tracing just generates
a lot of noise that I have to wade through.  Additionally, tracing can only identify a general
query pattern that is being non-performant, rather than an outlier (a partition with a ton
of tombstones).

On the mysql side, I've used tools like mysqldumpslow to aggregate slow queries and do analysis
of my system.  From an operational perspective this would help give feedback to developers.

> Slow query log
> --------------
>                 Key: CASSANDRA-6226
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: sankalp kohli
>            Priority: Minor
> We need a slow query log for Cassandra similar to the one in mysql. 
> Tracing does not work because you don't want to enable it for all the requests and want
to catch the slow queries. 
> We already have a JIRA to display queries which are going over lot of tombstones. But
a query can be slow also because it is returning lot of data. 
> We can store all the slow queries for a day in system table. 

This message was sent by Atlassian JIRA

View raw message