Hi, First look out for ways to reduce mutation size if possible (reducing batch size or reducing blob size). If you cant, then do the change and test it. More specifically focus on memory usage and gc pauses. If if looks ok then you are good to go.
regards, Laxmikant On Wed, Jul 10, 2019 at 6:21 PM Muralikrishna Gutha <muralikgu...@gmail.com> wrote: > We are running Cassandra: 2.1.15, We started noticing below errors, app is > writing larger mutations and before we take a route of increasing from 32MB > to 64MB for `commitlog_segment_size_in_mb` wanted to understand if there > are any cons by increasing it. Do we need to tweak any other parameters as > a result to this change ? > > > Caused by: java.lang.IllegalArgumentException: *Mutation of 19019986 > bytes is too large for the maximum size of 16777216* > at org.apache.cassandra.db.commitlog.CommitLog.add(CommitLog.java:221) > ~[apache-cassandra-2.1.15.jar:2.1.15] > at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:379) > ~[apache-cassandra-2.1.15.jar:2.1.15]``` > > Thanks for your time... > > Thanks > Murali Gutha > -- regards, Laxmikant Upadhyay
