Reads still need to satisfy quorum when you've specified quorum --
otherwise you have no consistency control.
Each read goes out to each node that has a replica of key (in your case
all) and then independently each node consults its row cache and either
returns cached data or has to go through the
Hi.
That is basically our set up. We'll be holding all data on all nodes.
My problem was more on how the cache would behave. I thought it might go
this way:
1. No cache hit
Read from 3 nodes to verify results are correct and then return. Write
result into RowCache.
2. Cache hit
Read from
If you're hitting 3/5 nodes, it sounds like you've set your replication
factor to 5. Is that what you're doing so you can have a 2-node outtage?
For a 5-node cluster, RF=5, each node will have 100% of your data (a second
DC is just a clone), so with a 3GB off-heap it means that 3GB / total would
I was reading through configuration tips for cassandra and decided to
use row-cache in order to optimize the read performance on my cluster.
I have a cluster of 10 nodes, each of them opeartion with 3 GB off-heap
using cassandra 2.4.1. I am doing local quorum reads, which means that I
will hit
