Re: QUORUM writes, QUORUM reads -- and eventual consistency

2012-08-25 Thread Guillermo Winkler
Isn't it cheaper to retry the mutation on _any exception_ than to have a transaction in place for the majority of non failing writes? The special case to be considered is obviously counters which are not idempotent https://issues.apache.org/jira/browse/CASSANDRA-2495 On Sat, Aug 25, 2012 at 4:

unsubscribe

2012-08-25 Thread Shen

Re: QUORUM writes, QUORUM reads -- and eventual consistency

2012-08-25 Thread Russell Haering
The "issue" is that it is possible for a quorum write to return an error, but for the result of the write to still be reflected in the view seen by the client. There is really no performant way around this (although reading at ALL can make it much less frequent). Guaranteeing complete success or fa

Re: QUORUM writes, QUORUM reads -- and eventual consistency

2012-08-25 Thread Guillermo Winkler
Hi Philip, >From http://wiki.apache.org/cassandra/ArchitectureOverview *Quorum write*: blocks until quorum is reached By my understanding if you _did_ a quorum write it means it successfully completed. Guille I *think* we're saying the same thing here. The addition of the word > "successful"