cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Yeksigian (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-9286) Add Keyspace/Table details to error message
Date Mon, 23 Nov 2015 21:26:11 GMT


Carl Yeksigian updated CASSANDRA-9286:
    Component/s: Observability

> Add Keyspace/Table details to error message
> ---------------------------------------------------------------
>                 Key: CASSANDRA-9286
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Observability
>            Reporter: sequoyha pelletier
>            Assignee: Carl Yeksigian
>            Priority: Minor
>             Fix For: 2.0.15, 2.1.6
>         Attachments: 9286-2.0-v2.txt, 9286-2.0.txt, 9286-2.1-v2.txt, 9286-2.1.txt
> The error message for too many element in a collection does not give keyspace or column
family information. This makes it a pain point to try to determine which table is the offending
> Example Error message:
> {noformat}
> ERROR [Native-Transport-Requests:809453] 2015-04-23 22:48:21,189
(line 116) Detected collection with 136234 elements, more than the 65535 limit. Only the first
65535 elements will be returned to the client. Please see
for more details.
> {noformat}
> Currently, to try to pinpoint the table in question. We need to trace all requests and
then try to match up the timestamps in the CQL tracing session with the log timestamps to
try and match. If prepared statements are used, this is a dead end due to the logged tracing
information missing the query. In which case, we have to look at other 3rd party methods for
capturing the queries to try and match up. This is extremely tedious when many tables have
collections and a high number of ops against them.
> Requesting that the error contain the keyspace.table name in the error message.

This message was sent by Atlassian JIRA

View raw message