Re: Basic question on distributed delete

2011-01-19 Thread Jonathan Ellis
Even without machines being down, the guarantee Cassandra gives you is exactly the ConsistencyLevel. Everything else is best-effort. In particular if you hammer Cassandra with more requests than it can fulfill, it will drop some instead of, say, running out of memory trying to queue them all up.

Re: Basic question on distributed delete

2011-01-19 Thread Scott McCarty
Okay, this helps. Cassandra works as I expected in the theoretically "pure" case (writing to the rest of the replicas in a background thread). I asked the question because we've been struggling to understand why we're seeing inconsistencies when we haven't had nodes go down, etc. (However, even

Re: Basic question on distributed delete

2011-01-19 Thread Peter Schuller
> When we do a delete on a column in the above configuration, the call to the > server won't return until 2 of the 3 replicas are written to unless there's > an error.  That part is well-documented and understood.  The question I have > is whether or not the last of the 3 replica nodes gets the del

Basic question on distributed delete

2011-01-19 Thread Scott McCarty
I've been searching on wikis and FAQs for a definitive answer to this and haven't found it yet so I thought I'd ask people here. We have a 5-node cluster set up with a replication factor of 3. We're doing write operations (using batch mutates that include deletions) with a QUORUM consistency leve