I have seen the following warn in system.log, as a temporary turn around i
increased commitlog_size in cassandra.yaml to 64, but how can i trace it
down ??? which appilcation is trying to write large writes and to which
keyspace and table it is trying to write ??
WARN [SharedPool-Worker-3] 2016-10-05 03:46:22,363
AbstractTracingAwareExecutorService.java:169 - Uncaught exception on thread
Thread[SharedPool-Worker-3,5,main]: {} java.lang.IllegalArgumentException:
Mutation of 19711728 bytes is too large for the maxiumum size of 16777216
at org.apache.cassandra.db.commitlog.CommitLog.add(CommitLog.java:221)
~[cassandra-all-2.1.8.689.jar:2.1.8.689]
at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:383)
~[cassandra-all-2.1.8.689.jar:2.1.8.689]
at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:363)
~[cassandra-all-2.1.8.689.jar:2.1.8.689]
at org.apache.cassandra.db.Mutation.apply(Mutation.java:214)
~[cassandra-all-2.1.8.689.jar:2.1.8.689]
at
org.apache.cassandra.db.MutationVerbHandler.doVerb(MutationVerbHandler.java:54)
~[cassandra-all-2.1.8.689.jar:2.1.8.689]
at
org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64)
~[cassandra-all-2.1.8.689.jar:2.1.8.689]
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown
Source) ~[na:1.8.0_92]
at org.apache.cassandra.concurrent.AbstractTracingAwareExecutorSe
rvice$FutureTask.run(AbstractTracingAwareExecutorService.java:164)
~[cassandra-all-2.1.8.689.jar:2.1.8.689]
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105)
[cassandra-all-2.1.8.689.jar:2.1.8.689]
at java.lang.Thread.run(Unknown Source) [na:1.8.0_92]
Thanks
James.
