cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick McFadin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6487) Log WARN on large batch sizes
Date Sun, 22 Dec 2013 03:19:51 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13855081#comment-13855081
] 

Patrick McFadin commented on CASSANDRA-6487:
--------------------------------------------

Yes that was in bytes. Just in my own experience, I don't recommend more than ~100 mutations
per batch. Doing some quick math I came up with 5k as 100 x 50 byte mutations. 

Totally up for debate.

> 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
>         Attachments: 6487_trunk.patch, 6487_trunk_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.1.5#6160)

Mime
View raw message