cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Joseph <>
Subject Fwd: WARN [SharedPool-Worker-3]
Date Tue, 18 Oct 2016 16:20:14 GMT
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 - 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(
      at org.apache.cassandra.db.Keyspace.apply(
      at org.apache.cassandra.db.Keyspace.apply(
      at org.apache.cassandra.db.Mutation.apply(
      at org.apache.cassandra.db.MutationVerbHandler.doVerb(
      at java.util.concurrent.Executors$
Source) ~[na:1.8.0_92]
      at org.apache.cassandra.concurrent.AbstractTracingAwareExecutorSe
      at Source) [na:1.8.0_92]


View raw message