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-13002) per table slow query times
Date Thu, 05 Oct 2017 01:45:00 GMT

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

Murukesh Mohanan commented on CASSANDRA-13002:
----------------------------------------------

Just checking to avoid confusion: do the updated patches still cause Cassandra to crash when
starting with data from a 3.0 instance?

> per table slow query times
> --------------------------
>
>                 Key: CASSANDRA-13002
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13002
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Observability
>            Reporter: Jon Haddad
>            Assignee: Murukesh Mohanan
>             Fix For: 4.x
>
>         Attachments: 0001-Add-per-table-slow_query_log_timeout_in_ms-property.patch,
0001-Add-per-table-slow_query_log_timeout_in_ms-property.patch, 0001-Add-per-table-slow_query_log_timeout_in_ms-property.patch
>
>
> CASSANDRA-12403 made it possible to log slow queries, but the time specified is a global
one.  This isn't useful if we know different tables have different access patterns, as we'll
end up with a lot of noise.  We should be able to override the slow query time at a per table
level.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message