The client should notice this on their side . If you want to see on the
server log one idea may be is to enable the debug mode .
You can set it specifically for org.apache.cassandra.transport
Something like nodetool setlogginglevel org.apache.cassandra.transport
DEBUG
If you are lucky enough :) (i.e. not too much chatter around the same
time) , you should see the query just before that WARN message appears in
log .
You can turn off the debugging once you get the info.
Good luck !!
On Mon, Sep 17, 2018 at 9:06 PM Saladi Naidu <naidusp2...@yahoo.com.invalid>
wrote:
> Any clues on this topic?
>
> Naidu Saladi
>
>
> On Thursday, September 6, 2018 9:41 AM, Saladi Naidu
> <naidusp2...@yahoo.com.INVALID> wrote:
>
>
> We are receiving following error
>
> 9140- at
> org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105)
> [apache-cassandra-3.0.10.jar:3.0.10]
>
> 9141- at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101]
>
> 9142:WARN [SharedPool-Worker-1] 2018-09-06 14:29:46,071
> AbstractLocalAwareExecutorService.java:169 - Uncaught exception on thread
> Thread[SharedPool-Worker-1,5,main]: {}
>
> 9143-java.lang.IllegalArgumentException: Mutation of 16777251 bytes is too
> large for the maximum size of 16777216
>
> 9144- at
> org.apache.cassandra.db.commitlog.CommitLog.add(CommitLog.java:256)
> ~[apache-cassandra-3.0.10.jar:3.0.10]
>
>
> I found following link that explained the cause
>
> By design intent the maximum allowed segment size is 50% of the configured
> commit_log_segment_size_in_mb. This is so Cassandra avoids writing segments
> with large amounts of empty space.
> To elaborate; up to two 32MB segments will fit into 64MB, however 40MB
> will only fit once leaving a larger amount of unused space.
>
> "I would like to find what table/column family this write/mutation is
> causing this error so that I can reach out to right application team, log
> does not provide any details regarding the mutation at all, is there a way
> to find that out
>
> Mutation of bytes is too large for the maxiumum size of
> <https://support.datastax.com/hc/en-us/articles/207267063-Mutation-of-x-bytes-is-too-large-for-the-maxiumum-size-of-y->
>
> Mutation of bytes is too large for the maxiumum size of
> Summary Apache Cassandra will discard mutations larger than a
> predetermined size. This note addresses why this h...
>
> <https://support.datastax.com/hc/en-us/articles/207267063-Mutation-of-x-bytes-is-too-large-for-the-maxiumum-size-of-y->
>
>
>
>
> Naidu Saladi
>
>
>
