cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject RE: lots of DigestMismatchException in cassandra3
Date Tue, 22 Nov 2016 06:30:46 GMT
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 cause you can think of?  Would it cause performance issue when lots of this
“Mismatch” happened?

Regards, Adeline

From: kurt Greaves []
Sent: Monday, November 21, 2016 5:02 PM
Subject: Re: lots of DigestMismatchException in cassandra3

Actually, just saw the error message in those logs and what you're looking at is probably<>

Kurt Greaves<><>

On 21 November 2016 at 08:59, kurt Greaves <<>>

That's a debug message. From the sound of it, it's triggered on read where there is a digest
mismatch between replicas. As to whether it's normal, well that depends on your cluster. Are
the nodes reporting lots of dropped mutations and are you writing at <QUORUM?

View raw message