cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kévin LOVATO (JIRA) <>
Subject [jira] [Commented] (CASSANDRA-6487) Log WARN on large batch sizes
Date Wed, 24 Sep 2014 09:08:34 GMT


Kévin LOVATO commented on CASSANDRA-6487:

We experienced some problems when using (ridiculously) big batches here, Cassandra was throwing
odd exceptions:
java.lang.IndexOutOfBoundsException: Invalid combined index of 1565817280, maximum is 482109
        at org.jboss.netty.buffer.SlicedChannelBuffer.<init>(
        at org.jboss.netty.buffer.HeapChannelBuffer.slice(
        at org.jboss.netty.buffer.AbstractChannelBuffer.readSlice(
        at org.apache.cassandra.transport.CBUtil.readValue(
        at org.apache.cassandra.transport.CBUtil.readValueList(
        at org.apache.cassandra.transport.messages.BatchMessage$1.decode(
        at org.apache.cassandra.transport.messages.BatchMessage$1.decode(
        at org.apache.cassandra.transport.Message$ProtocolDecoder.decode(
        at org.jboss.netty.handler.codec.oneone.OneToOneDecoder.handleUpstream(
        at org.jboss.netty.handler.codec.oneone.OneToOneDecoder.handleUpstream(
        at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(
        at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(
        at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$ Source)
        at Source)

We fixed our code so it behaved and stopped sending huge batches, but since it appears that
Cassandra can't handle too big batches, wouldn't it make more sense to simply refuse them
instead of warning / crashing ?

> Log WARN on large batch sizes
> -----------------------------
>                 Key: CASSANDRA-6487
>                 URL:
>             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

View raw message