After the old data came up we were able to delete it again. And it is
stable now.
We are in the process of upgrading to 1.0, but as you said that's a
painful process.
I just hope 0.6 will keep running till we're done with the upgrade.
Anyway thanks for the help.
Cheers,
Stefan
On 03/06/2012
> All our writes/deletes are done with CL.QUORUM.
> Our reads are done with CL.ONE. Although the reads that confirmed the old
> data were done with CL.QUORUM.
> According to
> https://svn.apache.org/viewvc/cassandra/branches/cassandra-0.6/CHANGES.txt
> 0.6.6 has the same patch
> for (CASSA
Hi Aaron,
Thanks for the quick reply.
All our writes/deletes are done with CL.QUORUM.
Our reads are done with CL.ONE. Although the reads that confirmed the
old data were done with CL.QUORUM.
According to
https://svn.apache.org/viewvc/cassandra/branches/cassandra-0.6/CHANGES.txt
0.6.6 has the s
> After we added a fourth node, keeping RF=3, some old data appeared in the
> database.
What CL are you working at ? (Should not matter too much with repair working,
just asking)
> We don't run compact on the nodes explicitly as I understand that running
> repair will trigger a
> major compact
Hi,
We were running a 3-node cluster of cassandra 0.6.13 with RF=3.
After we added a fourth node, keeping RF=3, some old data appeared in
the database.
As far as I understand this can only happen if nodetool repair wasn't
run for more than GCGraceSeconds.
Our GCGraceSeconds is set to the defau
