You can not be /mostly/ consistent readlike you can not be half-pregnant
or half transactional. You either are or you are not.
If you do not have enough nodes for a QUORUM the read fails. Thus you never
get stale reads you only get failed reads.
The dynamic snitch makes reads sticky at READ.ONE.
Hi Folks,
I'm trying to wrap my brain around how one would configure a Cassandra
cluster to support consistent reads in various cluster failure states.
(IE: Reads must see the most recent write.)
Gracefully handling a single node failure seems easy enough. Use
QUORUM (RF/2+1) for reads and