[
https://issues.apache.org/jira/browse/CASSANDRA-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013265#comment-15013265
]
Lyuben Todorov commented on CASSANDRA-6487:
-------------------------------------------
[~martin.grotzke] Yes the batch size is relevant in both scenario 1 and 2.
Remember it's a warning, you can tweek the settings to see increase the batch
size using the setting {{batch_size_warn_threshold_in_kb}}. Also notice that
the fail threshold is 10x the warn threshold by default
({{batch_size_fail_threshold_in_kb: 50}}).
> Log WARN on large batch sizes
> -----------------------------
>
> Key: CASSANDRA-6487
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6487
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Patrick McFadin
> Assignee: Lyuben Todorov
> Priority: Minor
> Fix For: 2.0.8, 2.1 beta2
>
> Attachments: 6487-cassandra-2.0.patch, 6487-cassandra-2.0_v2.patch
>
>
> Large batches on a coordinator can cause a lot of node stress. I propose
> adding a WARN log entry if batch sizes go beyond a configurable size. This
> will give more visibility to operators on something that can happen on the
> developer side.
> New yaml setting with 5k default.
> {{# Log WARN on any batch size exceeding this value. 5k by default.}}
> {{# Caution should be taken on increasing the size of this threshold as it
> can lead to node instability.}}
> {{batch_size_warn_threshold: 5k}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
