[ https://issues.apache.org/jira/browse/CASSANDRA-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038082#comment-14038082 ]
Jon Travis commented on CASSANDRA-6487: --------------------------------------- Does this make sense to log even in the case where the batch is Type.UNLOGGED? When writing as fast as I can, it sounds like a BatchStatement with a single execution is the fastest thing to do. However, I'm now getting these warnings. My options are to jack up the batch size threshold, or stop using batch statements.. > 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 > > 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.2#6252)