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
It saves a lot of information for each request thats traced so there is
significant overhead. 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
Personally I've found that using query timing + log aggregation on the
client side is more effective than trying to mess with tracing probability
in order to find a single query which has recently become a problem. I
recommend wrapping your session with something that can automatically log
the
Hello all,
My work will be deploying a cassandra cluster next year. Due to internal
wrangling we can't seem to agree on the hardware. The software hasn't been
finished, but management are asking for a ballpark figure for the hardware
costs.
The problem is the IT team are saying the nodes need to
Cassandra is a cluster itself, it's not necessary to have redundant each node.
Cassandra has replication for that. And also Cassandra is designed to run in
multiple data center - am think that redundant policy is applicable for you.
Only thing from your saying you can deploy is raid10, other
