The last time this came up on the list Jonathan Ellis said (something
along the lines of) if your application can't tolerate stale data then
you should read with a consistency level of QUORUM.
It would be nice if there was some sort of middle ground for an
application that can tolerate slightly st
On 10/22/10 2:55 PM, Craig Ching wrote:
Even better, I'd love a way to not allow B to be available
until replication is complete, can I detect that somehow?
Proposed and rejected a while back :
https://issues.apache.org/jira/browse/CASSANDRA-768
=Rob
Hi,
I'm testing Cassandra to ensure it fits my needs. One of the tests I
want to perform is writing while a node is down. Here's the scenario:
Cassandra 0.6.6
2 nodes
replication factor of 2
hinted handoff on
I load node A with 50,000 rows while B is shutdown (BTW, I'm using
CL.ONE during the
