It may be an indication of a lower-level problem in your cluster, e.g. flakey network causing FD false positives causing writes to be initially replicated to less than all 3 nodes.
On Sun, Sep 26, 2010 at 11:53 AM, Narendra Sharma <narendra.sha...@gmail.com> wrote: > We are seeing high number of DigestMismatchException on our Cassandra > deployment. We have a cluster of 4 nodes with RF=3 and we read/write in > Quorum. I understand some DigestMismatchException is normal and is the > mechanism for Cassandra to ensure consistency by doing read-repair. > > In our case, even though we have 4 clients, only the client that writes the > data, read the data because of request sharding at client end. So I would > expect the replication to happen fast and data be consistent on the 3 copies > before the read hits the cluster. The size of column value is approx 128K. > We verified multiple times that the timestamp of all the clients is in sync. > > Is this something to worry about? How do we troubleshoot if this an issue? > > > Thanks, > Naren > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
