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
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
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
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
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.com wrote:
Read repair will probably occur at that point (depending on your
config), which would cause
,
-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 elaborate specifically what happens in the case I
mentioned above to Dave?
thanks,
Ritesh
that you take when you use the 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 elaborate specifically what happens in the case I
,
Naren
On Wed, Feb 23, 2011 at 3:36 PM, Ritesh Tijoriwala
tijoriwala.rit...@gmail.com wrote:
Hi Anthony,
I am not talking about the case of CL ANY. I am talking about the case
where your consistency level is R + W N and you want to write to W nodes
but only succeed in writing to X
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 -
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
10 matches
Mail list logo