cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Murukesh Mohanan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13001) pluggable slow query logging / handling
Date Tue, 14 Feb 2017 10:08:41 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865514#comment-15865514
] 

Murukesh Mohanan commented on CASSANDRA-13001:
----------------------------------------------

I have a hacky WIP patch for this, but, looking at the Datastax {{node_slow_log}}, I think
it falls woefully short of what Datastax already does. The logging is currently done in the
{{MonitorableImpl}} class, which doesn't, as far as I can tell, have access to that much information.
Worse, even the query isn't really available, as [the comment on function that provides access
to it|https://github.com/apache/cassandra/blob/cassandra-3.10/src/java/org/apache/cassandra/db/ReadCommand.java#L616]
notes.
Right now my changes are confined to a single file, but doing what {{node_slow_log}} provides
would be more invasive. Thoughts? Should I try for it?

> pluggable slow query logging / handling
> ---------------------------------------
>
>                 Key: CASSANDRA-13001
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13001
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Jon Haddad
>
> Currently CASSANDRA-12403 logs slow queries as DEBUG to a file.  It would be better to
have this as an interface which we can log to alternative locations, such as to a table on
the cluster or to a remote location (statsd, graphite, etc).  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message