[
https://issues.apache.org/jira/browse/CASSANDRA-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059511#comment-15059511
]
Patrick McFadin commented on CASSANDRA-6487:
--------------------------------------------
[~martin.grotzke] and [~pragone] Sorry! I just caught these comments.
Valid points on a single partition and I think it warrants a change in the way
we log WARN and ERROR for batches. The original intent was to prevent horrible
anti-patterns on multi-partition batches. In the case of a single partition
update, the impact is only in network payload size. Since there is no need for
the coordinator to track all of the mutations across the batch partitions, the
load is much less.
I'll make an updated ticket to reflect that difference.
Thanks for the comments and raising this issue.
> 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)
