cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8011) Fail on large batch sizes
Date Wed, 02 Sep 2015 11:28:46 GMT

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

Benedict commented on CASSANDRA-8011:
-------------------------------------

This restriction seems to apply even when the batch covers only one partition. We shouldn't
really be upset at users sending large batch updates that are for a single partition, as artificially
separating the updates doesn't provide any benefit to Cassandra, and most likely pushes problems
onto the user.

> 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: 2.2.0 beta 1
>
>         Attachments: 8011-trunk-v2.txt, 8011-trunk-v3.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)

Mime
View raw message