[
https://issues.apache.org/jira/browse/CASSANDRA-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14175171#comment-14175171
]
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: https://issues.apache.org/jira/browse/CASSANDRA-6226
> 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
(v6.3.4#6332)
