cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Yeksigian (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-8930) Add a warn notification for clients
Date Mon, 04 May 2015 19:00:07 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-8930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Carl Yeksigian updated CASSANDRA-8930:
--------------------------------------
    Attachment: 8930-trunk.txt

I've attached a patch which adds a {{ClientWarn.warn()}} that buffers the messages and sends
it with the response to the client. It is active for v4 clients.

Added client warnings for batch log size and tombstone overwhelming warnings, as well as a
deprecation warning for using unlogged batches (was the motivation for looking at this).

> Add a warn notification for clients
> -----------------------------------
>
>                 Key: CASSANDRA-8930
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8930
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Carl Yeksigian
>              Labels: client-impacting, protocolv4
>             Fix For: 3.x
>
>         Attachments: 8930-trunk.txt
>
>
> Currently, if a query generates a warning, it is going to be logged server side. If the
person writing the query is not the admin, that warning isn't going to have an impact on the
query, and we're just going to fill up the server logs.
> We should push these warnings back to the client so the driver users can make necessary
changes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message