Has anyone seen this assert failure below? Seems like a race to delete a commit
log file. I am running 0.7-beta1, I was wondering if this has already been
fixed, in which case I can merge that fix in my current tree.
INFO [FLUSH-WRITER-POOL:1] 2010-12-14 03:12:38,364 Memtable.java (line 157)
C
I have done some bulk write performance tests and I saw background compaction
making a big detrimental impact on the write performance. I was also wondering
if there is a tunable to limit the frequency of the compaction on the sstables.
If not, then adding such a configuration option would also
liar with HTTP. I think vector clocks
with client merge give you essentially the same functionality, but in a way
that fits much more nicely with the rest of the Cassandra architecture. CAS
really exacerbates Cassandra's weaknesses.
Mike
On Tue, Jun 22, 2010 at 4:52 PM, Rishi Bhardwaj wro
hat.
R: That sounds great. I am definitely going to look into this and report back
if I have a good solution.
Thanks,
Rishi
From: Sylvain Lebresne
To: dev@cassandra.apache.org
Sent: Tue, June 22, 2010 1:21:51 AM
Subject: Re: Atomic Compare and Swap
On Mo
-and-transactions-over-cassandra-using-cages/
I guess, you will like it.
2010/6/22 Rishi Bhardwaj
> I am definitely interested in taking this work up. I believe the CAS
> functionality would help in a lot of different scenarios and could help
> avoid use of other external services (like
rate higher than
a quorum. One pays the price for a more complex write path to obtain the
requisite guarantee.
On Jun 21, 2010, at 4:03 AM, Rishi Bhardwaj wrote:
>
> Heres another thought I had, if say the user always wrote with quorum (or to
> all) nodes then can't we impleme
wap
That is impossible to implement without making the write path at least as slow
as the read path. Things like this typically get layed on Cassandra by using an
external locking framework, like Zookeeper.
-Original Message-
From: Rishi Bhardwaj
Date: Sun, 20 Jun 2010 14:57:46
To:
Rep
Hi
I was wondering if Cassandra has any plans for supporting atomic compare and
swap operation on a column value? Compare could be on timestamp for the column
or the column value itself and the write of course is on the column value + a
new timestamp. If there are no plans on supporting such an
