In one of our test clusters we had a damaged commit log disks in one of the
nodes.
We have replication factor = 2 in this cluster, and write with consistency
level = ONE. So we expected writes will not be affected by such an issue. But
what actually happened is that the client that was writing
How about using Snowflake to generate the transaction ids:
https://github.com/twitter/snowflake
From: Kent Narling [mailto:kent.narl...@gmail.com]
Sent: Thursday, July 28, 2011 5:46 PM
To: user@cassandra.apache.org
Subject: Using Cassandra for transaction logging, good idea?
Hi!
I am
logs ?
Some background about handling disk fails
https://issues.apache.org/jira/browse/CASSANDRA-809
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 1 Aug 2011, at 08:13, Lior Golan wrote:
In one of our test clusters we had
@cassandra.apache.org
Subject: Re: How to keep only exactly column of key
On Tue, Jul 19, 2011 at 10:15 AM, Lior Golan lio...@taboola.com wrote:
Can't this capping be done (approximately) during compaction.
Something
like:
1. Ability to define for a column family that it's a capped
Can't this capping be done (approximately) during compaction. Something like:
1. Ability to define for a column family that it's a capped collection
with at most N columns per row
2. During write - just add the column
3. During reads - get a slice with the most recent / top N
Can you share what numbers you are now getting?
-Original Message-
From: markuskl...@gmail.com [mailto:markuskl...@gmail.com] On Behalf Of Markus
Klems
Sent: Saturday, February 19, 2011 10:53 AM
To: user@cassandra.apache.org
Subject: Re: Benchmarking Cassandra with YCSB
Hi,
we sorted
