Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 4 May 2015 20:00:08 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12826549.1430489039000.73621.1430769608390@Atlassian.JIRA>
In-Reply-To: <JIRA.12826549.1430489039000@Atlassian.JIRA>
References: <JIRA.12826549.1430489039000@Atlassian.JIRA>
 <JIRA.12826549.1430489039019@arcas>
Subject: [jira] [Commented] (CASSANDRA-9282) Warn on unlogged batches
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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: https://issues.apache.org/jira/browse/CASSANDRA-9282
>             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
(v6.3.4#6332)