Fwd: WARN [SharedPool-Worker-3] AbstractTracingAwareExecutorService.java

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

WARN [SharedPool-Worker-3] AbstractTracingAwareExecutorService.java

I am seeing following warn in system.log, as a temporary turn around i can increase 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-1

How to find the reason for mutation drops ??

I am seeing mutation drops on one of my nodes in the cluster, the load is low no Gc pauses no wide partitions either, so can i debug what is the reason for mutation drops ?? i ran nodetool tpstats only one node out of 9 is dropping rest 8 nodes in the cluster are having 0 mutation drops. How can

when taking backups using snapshot if the sstable gets compacted will nodetool snapshot hung ??

Hai we are taking backups using nodetool snapshots but i occasionally see that my script pauses while taking a snapshot of a CF, is this because when it is taking snapshot does the sstables got compacted to a different one so it couldn't find that particular sstable on which it is taking snapshot