Re: New thread for : How does Cassandra handle failure during synchronous writes

thanks Narendra. I read again the wiki quote you pasted below and now it does make sense. Cassandra's design behavior is to propagate the failed write if it was ever written successfully to atleast one server. I was having hard time trying to work around this but I guess I am starting to think the

Re: New Chain for : Does Cassandra use vector clocks

Thanks all for good detail and clarification. I just wanted to get things clear and understand correctly what is the expected behavior when working with Cassandra against various failure conditions so that application can be designed accordingly and provide proper locking/synchronization if require

Re: New Chain for : Does Cassandra use vector clocks

I was about to ask what Anthony's latest post below captures - if we don't have vector clocks and no locking, how does cassandra prevent/detect conflicts? This is somewhat related to the question I asked in last post - http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/How-does-Cassan

Re: How does Cassandra handle failure during synchronous writes

ritten to node1. >> c. Read with CL = QUORUM. If read hits node1 and node2/node3, new data >> that was written to node1 will be returned. >> >> HTH! >> >> Thanks, >> Naren >> >> >> >> On Wed, Feb 23, 2011 at 3:36 PM, Ritesh Tijoriw

Re: How does Cassandra handle failure during synchronous writes

>>> At CL ANY - if all endpoints are down - a HH is written. And it is a >>> successful write - not a failed write. >>> >>> Now that does not guarantee a READ of the value just written - but that >>> is a risk that you take when you use the ANY CL! >>

Re: How does Cassandra handle failure during synchronous writes

he ANY CL! > > HTH, > > -JA > > > On Wed, Feb 23, 2011 at 4:40 PM, Ritesh Tijoriwala < > tijoriwala.rit...@gmail.com> wrote: > >> hi Anthony, >> While you stated the facts right, I don't see how it relates to the >> question I ask. Can you elabora

Re: How does Cassandra handle failure during synchronous writes

case) only applies after Quorum is met - so a Quorum R is > not dependent on the down node being up, and having got the hint. > > Hope I state this appropriately! > > HTH, > > -JA > > > On Wed, Feb 23, 2011 at 3:39 PM, Ritesh Tijoriwala < > tijoriwala.rit...@gmail.co

Re: Is Cassandra suitable for my problem?

Hi Alexandru, I feel Cassandra can certainly be used to solve the problem you have but if your requires are not very strict, you need very high throughput and its okay for you to lose some data occasionally due to machine crash, then I recommend you look at Redis (http://redis.io/). It is a high pe

Re: How does Cassandra handle failure during synchronous writes

> Read repair will probably occur at that point (depending on your config), which would cause the newest value to propagate to more replicas. Is the newest value the "quorum" value which means it is the old value that will be written back to the nodes having "newer non-quorum" value or the newest

Patterns for writing enterprise applications on cassandra

Hi, I have general questions on writing enterprise applications on cassandra. I come from a background which involves writing enterprise applications using DBMS. What are the general patterns people follow in Cassandra world when migrating a code that is within transaction boundaries in a traditio