Txs Sylvain. Interesting feedback
For now higher consistency level is not fault tolerant (two node setup) but
worth to consider for other deployments.
Further investigation learns that system has quit some iowaits. It seems
that we are pushing it to far.
It is obvious that counter cf's increments
>
> To my understanding client will not be notified because this read step is
> asynchronously.
Yes, though for the record it's actually synchronous if you use anything
else than CL.ONE.
> Also the other replica cannot be updated properly (replicate-on-write
> stage is backing up).
> Question i
Hi
We are running a Cassandra 1.0.7, 2 node setup on EC2 using ephemeral
disks for storage.
Debugging inconsistent dara between 2 nodes we saw logging below.
Following the counter CF design, I assume this means the READ step
reconciliating the memtable value with the SSTables on the replica
rec
