/doanduyhai/Achilles/wiki/Statements-Logging-and-Tracing#dynamic-statements-logging
On Mon, Nov 10, 2014 at 3:52 PM, Johnny Miller johnny.p.mil...@gmail.com
wrote:
Be cautious enabling query tracing. Great tool for dev/testing/diagnosing
etc.. - but it does persist data to the system_traces
contribute to the slowness?
thanks
On Mon, Nov 10, 2014 at 7:21 AM, DuyHai Doan doanduy...@gmail.com wrote:
As Jonathan said, it's better to activate query tracing client side. It'll
give you better flexibility of when to turn on off tracing and on which
table. Server-side tracing is global
On Mon, Nov 10, 2014 at 7:21 AM, DuyHai Doan doanduy...@gmail.com
wrote:
As Jonathan said, it's better to activate query tracing client side.
It'll give you better flexibility of when to turn on off tracing and on
which table. Server-side tracing is global (all tables
Be cautious enabling query tracing. Great tool for dev/testing/diagnosing etc..
- but it does persist data to the system_traces keyspace with a TTL of 24 hours
and will, as a consequence, consume resources.
http://www.datastax.com/dev/blog/advanced-request-tracing-in-cassandra-1-2
http
As Jonathan said, it's better to activate query tracing client side. It'll
give you better flexibility of when to turn on off tracing and on which
table. Server-side tracing is global (all tables) and probabilistic, thus
may not give satisfactory level of debugging.
Programmatically it's pretty
is there any significant performance penalty if one turn on Cassandra
query tracing, through DataStax java driver (say, per every query request
of some trouble query)?
More sampling seems better but then doing so may also slow down the system
in some other ways?
thanks
On Fri, Nov 7, 2014 at 9:35 AM, Jimmy Lin y2klyf+w...@gmail.com wrote:
is there any significant performance penalty if one turn on Cassandra
query tracing, through DataStax java driver (say, per every query request
of some trouble query)?
What does 'significant' mean in your sentence? I'm
y2klyf+w...@gmail.com wrote:
is there any significant performance penalty if one turn on Cassandra
query tracing, through DataStax java driver (say, per every query request
of some trouble query)?
More sampling seems better but then doing so may also slow down the system
in some other ways
turn on Cassandra
query tracing, through DataStax java driver (say, per every query request
of some trouble query)?
More sampling seems better but then doing so may also slow down the
system in some other ways?
thanks
