Hi Kurt,
Thank you for the suggestion. I ran repair on all the 4 nodes, and after the
repair, the error “Corrupt empty row found in unfiltered partition”
disappeared, but the “Mismatch” stopped for a little while and came up again.
When we changed both the “dclocal_read_repair_chance” and the
“r
Hi Kurt,
Thank you for the information, but the error “Corrupt empty row found in
unfiltered partition” seems not related to the “Mismatch”; the time they
occurred didn’t match. We use “QUORUM” consistency level for both read and
write and I didn’t notice any failed writing in the log. Any other
Hi Tommy,
Thank you for the reply, but I don't think this is the reason, because we don't
have any static column.
--
Regards, Adeline
From: Tommy Stendahl [mailto:tommy.stend...@ericsson.com]
Sent: Thursday, November 17, 2016 5:16 PM
To: user@cassandra.apache.org
Subject: Re: lots of DigestMis
Hi,
We are using Cassandra 3.7 and we have a single datacenter of 4 nodes, RF =3,
and the consistency level is quorum.
I found lots of DigestMismatchException in debug.log, as below:
DEBUG [ReadRepairStage:11] 2016-11-17 08:24:57,066 ReadCallback.java:235 -
Digest mismatch:
org.apache.cassandra.
From: Pan, Adeline (TR Technology & Ops)
Sent: Tuesday, September 06, 2016 12:34 PM
To: 'user@cassandra.apache.org'
Cc: Yang, Ling (TR Technology & Ops)
Subject: FW: WriteTimeoutException with LOCAL_QUORUM
Hi All,
I hope you are doing well today, and I need your help.
We were using Cassandra 1
