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 [mailto:k...@instaclustr.com] Sent: Monday, November 21, 2016 5:02 PM To: user@cassandra.apache.org Cc: tommy.stend...@ericsson.com Subject: Re: lots of DigestMismatchException in cassandra3 Actually, just saw the error message in those logs and what you're looking at is probably https://issues.apache.org/jira/browse/CASSANDRA-12694<https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_CASSANDRA-2D12694&d=CwMFaQ&c=4ZIZThykDLcoWk-GVjSLm9hvvvzvGv0FLoWSRuCSs5Q&r=552xSDXEzKpvsyZM5wpE0TGEUDzVsX35L-K72hRjpLc&m=Km5uRGlDf2EjQFx7dbIrLzNfL6khh5OKA2sJk59l8-w&s=tMf24yohd0jRGCBo_pzYdRMw52h3NCImPOGXjy1SAsc&e=> Kurt Greaves k...@instaclustr.com<mailto:k...@instaclustr.com> www.instaclustr.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.instaclustr.com&d=CwMFaQ&c=4ZIZThykDLcoWk-GVjSLm9hvvvzvGv0FLoWSRuCSs5Q&r=552xSDXEzKpvsyZM5wpE0TGEUDzVsX35L-K72hRjpLc&m=Km5uRGlDf2EjQFx7dbIrLzNfL6khh5OKA2sJk59l8-w&s=TwJ80glB0cSS0rW6jU1MGnlLWUtVYL1J7061vp2e_rI&e=> On 21 November 2016 at 08:59, kurt Greaves <k...@instaclustr.com<mailto:k...@instaclustr.com>> wrote: 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?
