Re: query tracing

aturated the disk IO, other part of the >> tables will see similar effect but we didn't see it. >> is there any table specific factor may contribute to the slowness? >> >> thanks >> >> >> >> >> >> >> >> >> On Mon, Nov 10, 20

Re: query tracing

't see it. > is there any table specific factor may contribute to the slowness? > thanks > On Mon, Nov 10, 2014 at 7:21 AM, DuyHai Doan wrote: >> As Jonathan said, it's better to activate query tracing client side. It'll >> give you better flexibility of when to turn

Re: query tracing

saturated the disk IO, other part of the tables will see similar effect but we didn't see it. is there any table specific factor may contribute to the slowness? thanks On Mon, Nov 10, 2014 at 7:21 AM, DuyHai Doan wrote: > As Jonathan said, it's better to activate query tracin

Re: query tracing

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. Program

Re: query tracing

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 <h

Re: query tracing

ad. If you start at a low probability and move it up > based on the load impact it will provide a lot of insight and you can > control the cost. > > --- > Chris Lohfink > > On Fri, Nov 7, 2014 at 11:35 AM, Jimmy Lin wrote: > >> is there any significant performance

Re: query tracing

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? > > thanks > > >

Re: query tracing

On Fri, Nov 7, 2014 at 9:35 AM, Jimmy Lin 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 sentenc

query tracing

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