Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 29 Sep 2014 18:38:34 +0000 (UTC)
From: "Carl Yeksigian (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12744363.1411756964000.147333.1412015914169@Atlassian.JIRA>
In-Reply-To: <JIRA.12744363.1411756964000@Atlassian.JIRA>
References: <JIRA.12744363.1411756964000@Atlassian.JIRA>
 <JIRA.12744363.1411756964691@arcas>
Subject: [jira] [Updated] (CASSANDRA-8011) Fail on large batch sizes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Carl Yeksigian updated CASSANDRA-8011:
--------------------------------------
    Reviewer: sankalp kohli

> Fail on large batch sizes 
> --------------------------
>
>                 Key: CASSANDRA-8011
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8011
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Patrick McFadin
>            Assignee: Carl Yeksigian
>            Priority: Minor
>             Fix For: 3.0
>
>         Attachments: 8011-trunk-v2.txt, 8011-trunk.txt
>
>
> Related to https://issues.apache.org/jira/browse/CASSANDRA-6487
> Just education alone is not going to stop some of the largest batch sizes from being used. Just like we have a tombstone fail threshold, I propose that we have a batch size fail threshold.
> Maybe 10x warn?
> {{batch_fail_threshold: 50k}}


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