Cassandra does not have any automatic rollback of partial work for a failed
write request, if with CL=ALL - that just assures that you will get an
error indication if not all the writes succeed. You do need to keep
retrying failed writes until they succeed. Otherwise the partial work will
still be
Dear Jack,
Thanks!
My keyspace is such as:
test@cqlsh> DESC KEYSPACE sky ;
CREATE KEYSPACE sky WITH replication = {'class': 'SimpleStrategy',
'replication_factor': '3'} AND durable_writes = true;
CREATE TABLE sky.user1 (pati int, uuid text, name text, name2 text,
PRIMARY KEY (pati, u
You have three choices:
1. Insert with CL=ALL, with client-level retries if the write fails due to
the cluster being overloaded.
2. Insert with CL=QUORUM and then run repair after all data has been
inserted.
3. Lower your insert rate in your client so that the cluster can keep up
with your inserts
Hi all,
I have a C* cluster with 6 nodes. My cassandra version is 2.1.1. I start 50
threads to insert datas into C* cluster, each thread inserts about up to 100
million rows with the same partition key. After inserting all the datas, I
start another app with 50 threads to export all the dat
