Note that article pretty much covers it all; the nice thing about rapid-read
protection is that the dynamic snitch works on a per node statistics level to
pick which node(s) (in this case one), so a single poorly performing table
(perhaps corrupted SSTables on that node causing no responses and
If you are using cqlsh, you can get a look at what's happening behind the
scenes by enabling tracing with 'tracing on;' before executing a query. In
this scenario you'll see 'Sending message to [ip address]' for each of the
replicas.
On Fri, Mar 7, 2014 at 5:44 PM, Jonathan Lacefield
Yikes my apologies. B is not the answer
On Mar 7, 2014, at 8:24 PM, Russell Hatch rha...@datastax.com wrote:
If you are using cqlsh, you can get a look at what's happening behind the
scenes by enabling tracing with 'tracing on;' before executing a query. In
this scenario you'll see 'Sending
Actually, this is tunable in = 2.0.2 ;)
http://www.datastax.com/dev/blog/rapid-read-protection-in-cassandra-2-0-2
Michael
On 03/07/2014 07:33 PM, Jonathan Lacefield wrote:
Yikes my apologies. B is not the answer
On Mar 7, 2014, at 8:24 PM, Russell Hatch rha...@datastax.com
