cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Albert P Tobey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6487) Log WARN on large batch sizes
Date Sat, 14 Dec 2013 00:27:09 GMT

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

Albert P Tobey commented on CASSANDRA-6487:
-------------------------------------------

If it's not out of the way, it would help to include the keyspace and column family and maybe
the session ID/info.

> 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
>            Priority: Minor
>
> 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.4#6159)

Mime
View raw message