Thanks Doan, will try to enable slow query for app side and will let you
know if it helps or not.
Thanks
James.
On Wed, Oct 19, 2016 at 2:59 AM, DuyHai Doan wrote:
> "which appilcation is trying to write large writes and to which keyspace
> and table it is trying to write ??"
>
> --> I don't t
"which appilcation is trying to write large writes and to which keyspace
and table it is trying to write ??"
--> I don't think there is something such as audit trail for each CQL
query.
You may want to enable slow query logger on the client side (driver side)
and bet on the fact that the queries
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
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
