You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jon Haddad (JIRA)" <ji...@apache.org> on 2017/03/02 18:00:50 UTC
[jira] [Commented] (CASSANDRA-13001) pluggable slow query logging /
handling
[ https://issues.apache.org/jira/browse/CASSANDRA-13001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892695#comment-15892695 ]
Jon Haddad commented on CASSANDRA-13001:
----------------------------------------
The easiest code to look at is probably the seed provider:
{code}
# constructor that takes a Map<String, String> of parameters will do.
seed_provider:
# Addresses of hosts that are deemed contact points.
# Cassandra nodes use this list of hosts to find each other and learn
# the topology of the ring. You must change this if you are running
# multiple nodes!
- class_name: org.apache.cassandra.locator.SimpleSeedProvider
{code}
It's a very, very simple interface, where implementation is provided by the codebase and users can drop in their own if they want.
> 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)