Hello Jonathan,
Thanks for your quick reply. Since consistency is tunable by making
tradeoffs with latency and availability, it lead me to think about how to
improve the consistency level (better than eventual consistency) while
guarantee that latency and availability won't be affected much. So no
2 node cluster. RF=2. Take one node down. Do a write. Take the other
node down. Do a read. It will be stale since the node that is up missed
the original write, and you took the node that did see the write down
before it could replay to it.
This is by design though so I'm curious what kind
Hi there,
I currently research on the improvement of consistency level of Cassandra.
Since I am new to C*, does anyone know how to reproduce the stale reads on
the cluster? Is there a transaction lib that can be loaded into it and
reproduce the stale reads?
***TEST environment***
AWS 3 instances
