[
https://issues.apache.org/jira/browse/CASSANDRA-8011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151258#comment-14151258
]
sankalp kohli commented on CASSANDRA-8011:
------------------------------------------
Some nits
1) In your comment I think you mean "batch_size_fail_threshold_in_kb" and not
"batch_size_file_threshold_in_kb"
2) We should also expose changing this via JMX like we do for
TombstoneFailureThreshold.
3) When we encounter TombstoneFailureThreshold, we clearly write in the
exception like " (see tombstone_warn_threshold)". We should add the same for
this.
> 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.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)
