I see no dropped mutation in any of the nodes:

Message type           Dropped
RANGE_SLICE                  0
READ_REPAIR                  0
PAGED_RANGE                  0
BINARY                       0
READ                         0
MUTATION                     0
_TRACE                       0
REQUEST_RESPONSE             0
COUNTER_MUTATION             0

On Tue, Oct 6, 2015 at 5:35 PM, Kiran mk <coolkiran2...@gmail.com> wrote:

> Do you see more dropped mutation messages in nodetool tpstats output.
> On Oct 6, 2015 7:51 PM, "George Sigletos" <sigle...@textkernel.nl> wrote:
>
>> Hello,
>>
>> I have been frequently receiving those warnings:
>>
>> java.lang.IllegalArgumentException: Mutation of 35141120 bytes is too
>> large for the maxiumum size of 33554432
>>  at org.apache.cassandra.db.commitlog.CommitLog.add(CommitLog.java:221)
>> ~[apache-cassandra-2.1.9.jar:2.1.9]
>>     at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:383)
>> ~[apache-cassandra-2.1.9.jar:2.1.9]
>>     at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:363)
>> ~[apache-cassandra-2.1.9.jar:2.1.9]
>>     at org.apache.cassandra.db.Mutation.apply(Mutation.java:214)
>> ~[apache-cassandra-2.1.9.jar:2.1.9]
>>     at
>> org.apache.cassandra.db.MutationVerbHandler.doVerb(MutationVerbHandler.java:54)
>> ~[apache-cassandra-2.1.9.jar:2.1.9]
>>     at
>> org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64)
>> ~[apache-cassandra-2.1.9.jar:2.1.9]
>>     at java.util.concurrent.Executors$RunnableAdapter.call(Unknown
>> Source) ~[na:1.7.0_75]
>>     at
>> org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164)
>> ~[apache-cassandra-2.1.9.jar:2.1.9]
>>     at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105)
>> [apache-cassandra-2.1.9.jar:2.1.9]
>>     at java.lang.Thread.run(Unknown Source) [na:1.7.0_75]
>>
>> Sometimes I can trigger them myself by trying to add the contents of  a
>> text document that is less than 1 MB.
>>
>> Initially I did increase the "commitlog_segment_size_in_mb" from 32 to
>> 64. Thinking to further increase it to 96.
>>
>> But would that be a solution to the problem? What could be possibly
>> causing this?
>>
>> Thank you,
>> George
>>
>

Reply via email to