cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9282) Warn on unlogged batches
Date Mon, 04 May 2015 20:00:08 GMT


Jonathan Ellis commented on CASSANDRA-9282:

I was thinking we'd want to do this in StorageProxy to handle Thrift as well as CQL, but on
second thought I am okay doing it for CQL only.  Presumably Thrift users already have the
scars from this and have learned their lesson by now.

However, it would be useful to get a little more out of the warning message, and to give people
a pointer to the right fix.  {{Unlogged batch covering 100 partitions detected, starting with
INSERT INTO USERS.  You probably want to use a logged batch for atomicity, or asynchronous
writes for performance.}}

> Warn on unlogged batches
> ------------------------
>                 Key: CASSANDRA-9282
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>            Reporter: Jonathan Ellis
>            Assignee: T Jake Luciani
>             Fix For: 2.1.x
> At least until CASSANDRA-8303 is done and we can block them entirely, we should log a
warning when unlogged batches across multiple partition keys are used.  This could either
be done by backporting NoSpamLogger and blindly logging every time, or we could add a threshold
and warn when more than 10 keys are seen.

This message was sent by Atlassian JIRA

View raw message