[
https://issues.apache.org/jira/browse/CASSANDRA-15057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Schoening updated CASSANDRA-15057:
---------------------------------------
Resolution: Duplicate
Status: Resolved (was: Open)
Closing this as a duplicate as it was addressed with
[CASSANDRA-18219|https://issues.apache.org/jira/browse/CASSANDRA-18219]
> Log the query when warning about aggregate on multiple partition keys
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-15057
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15057
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Interpreter
> Reporter: GANGADHARA
> Priority: Normal
> Fix For: 5.x
>
>
> We have 05 node single DC Apache Cassandra cluster with version 2.2.5
> running on Ubuntu (4.15.0-1013-azure #13~16.04.2-Ubuntu SMP Wed May 30
> 01:39:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux).
>
> If we look at system.log file always we see WARNING of Aggregation query used
> on multiple partition keys (IN restriction) on all nodes .
> How to enable tracing/debugging and capture the full CQL Select Statement
> which is flooding the system.log file .
> I donot have Opscenter , or dev center or any other monitoring tool
> except nodetool .
>
> Are there any direct ways to find out what are the CQL running at a given
> current point in time on any Cassandra node
>
> WARN [SharedPool-Worker-2] 2019-03-19 08:16:06,935 SelectStatement.java:258
> - Aggregation query used on multiple partition keys (IN restriction)
> WARN [SharedPool-Worker-1] 2019-03-19 08:16:32,715 SelectStatement.java:258
> - Aggregation query used on multiple partition keys (IN restriction)
> WARN [SharedPool-Worker-2] 2019-03-19 08:16:47,666 SelectStatement.java:258
> - Aggregation query used on multiple partition keys (IN restriction)
> WARN [SharedPool-Worker-2] 2019-03-19 08:17:06,022 SelectStatement.java:258
> - Aggregation query used on multiple partition keys (IN restriction)
> WARN [SharedPool-Worker-1] 2019-03-19 08:17:36,642 SelectStatement.java:258
> - Aggregation query used on multiple partition keys (IN restriction)
> WARN [SharedPool-Worker-6] 2019-03-19 08:18:20,990 SelectStatement.java:258
> - Aggregation query used on multiple partition keys (IN restriction)
> WARN [SharedPool-Worker-2] 2019-03-19 08:20:44,853 SelectStatement.java:258
> - Aggregation query used on multiple partition keys (IN restriction)
> WARN [SharedPool-Worker-2] 2019-03-19 08:21:29,083 SelectStatement.java:258
> - Aggregation query used on multiple partition keys (IN restriction)
> WARN [SharedPool-Worker-1] 2019-03-19 08:21:46,911 SelectStatement.java:258
> - Aggregation query used on multiple partition keys (IN restriction)
> WARN [SharedPool-Worker-3] 2019-03-19 08:21:59,935 SelectStatement.java:258
> - Aggregation query used on multiple partition keys (IN restriction)
> WARN [SharedPool-Worker-2] 2019-03-19 08:22:13,693 SelectStatement.java:258
> - Aggregation query used on multiple partition keys (IN restriction)
> WARN [SharedPool-Worker-1] 2019-03-19 08:22:48,263 SelectStatement.java:258
> - Aggregation query used on multiple partition keys (IN restriction)
> WARN [SharedPool-Worker-13] 2019-03-19 08:46:11,379 SelectStatement.java:258
> - Aggregation query used on multiple partition keys (IN restriction)
> WARN [SharedPool-Worker-1] 2019-03-19 08:47:38,160 SelectStatement.java:258
> - Aggregation query used on multiple partition keys (IN restriction)
>
>
> Thanks
> Gangadhara
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
