[
https://issues.apache.org/jira/browse/CASSANDRA-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039360#comment-14039360
]
Jon Travis commented on CASSANDRA-6487:
---------------------------------------
I'm batching on a single partition only.
I have a table defined as:
CREATE TABLE store.blobs (
account_name text,
m_guid text,
m_blob text,
PRIMARY KEY (account_name,
m_guid))
I am using a prepared statement with an unlogged batch to insert many blobs
into the same account at all once:
INSERT INTO blobs (account_name, m_guid, m_blob) VALUES (?, ?, ?)
My understanding is that this is a pretty decent way of doing it:
http://www.datastax.com/dev/blog/client-side-improvements-in-cassandra-2-0
(re Batching Prepared Statements).
I could do these all individually, but there would clearly be some overhead.
So, the options are to not use the prepared statement / batch, jack up the
threshold, or change the Cassandra code to avoid logging on unlogged batches..
> 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)
