[
https://issues.apache.org/jira/browse/CASSANDRA-12403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15411112#comment-15411112
]
Shogo Hoshii commented on CASSANDRA-12403:
------------------------------------------
Hello [~ifesdjeen]
I appreciate your advice.
It is very useful in the case cassandra operator can access logs in client
server.
But I cannot do that because in my company my team(operators) has a lot of
users from different departments and operators do not have permission to client
servers.
And it is also difficult for my team to let all of users to use specific driver
because the organisations are separated.
(I guess some of other cassandra operators are in same circumstance as my team
is.)
So I would like to say we need to log slow query in server side.
> Slow query detecting
> --------------------
>
> Key: CASSANDRA-12403
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12403
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Shogo Hoshii
> Assignee: Shogo Hoshii
> Attachments: sample.log, slow_query.patch
>
>
> Hello,
> In cassandra production environment, users sometimes build anti-pattern
> tables and throw queries in inefficient manners.
> So I would like to suggest a feature that enables to log slow query.
> The feature can help cassandra operators to identify bad query patterns.
> Then operators can give advices about queries and data model to users who
> don't know cassandra so much.
> This ticket is related to CASSANDRA-6226, and I focus on detecting bad query
> patterns, not aborting them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
