cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Haddad (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13001) pluggable slow query logging / handling
Date Tue, 28 Feb 2017 16:12:45 GMT

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

Jon Haddad commented on CASSANDRA-13001:
----------------------------------------

So in Cassandra, when we talk about something being pluggable, we typically mean the following:

1. It's going to be java code
2. the pluggable thing implements an interface defined in cassandra.
3. the class would be compiled and dropped in lib (loaded into classpath automatically)
4. The class can be specified in the yaml and is loaded by {{Class.forName()}} to pull the
interface in

We would need to convert the current slow query logger into a class of the defined interface
and have it be the default if no class is specified in the yaml.

Other classes could be written later to do things like implement the metrics library, use
statsd, or send logs to the ELK stack.

Does that help?

> 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
>            Assignee: Murukesh Mohanan
>             Fix For: 4.0
>
>         Attachments: 0001-Add-multiple-logging-methods-for-slow-queries-CASSAN.patch
>
>
> 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