ay a tax that really
is associated with writing activity.
From: Carl Mueller
Reply-To: "user@cassandra.apache.org"
Date: Monday, December 9, 2019 at 3:18 PM
To: "user@cassandra.apache.org"
Subject: Re: Seeing tons of DigestMismatchException exceptions after upgrading
from
Reply-To: "user@cassandra.apache.org"
Date: Monday, December 9, 2019 at 3:18 PM
To: "user@cassandra.apache.org"
Subject: Re: Seeing tons of DigestMismatchException exceptions after upgrading
from 2.2.13 to 3.11.4
Message from External Sender
My speculation on rapidly
My speculation on rapidly churning/fast reads of recently written data:
- data written at quorum (for RF3): write confirm is after two nodes reply
- data read very soon after (possibly code antipattern), and let's assume
the third node update hasn't completed yet (e.g. AWS network "variance").
Hello,
As part of the final stages of our 2.2 --> 3.11 upgrades, one of our
clusters (on AWS/ 18 nodes/ m4.2xlarge) produced some post-upgrade fits. We
started getting spikes of Cassandra read and write timeouts despite the
fact the overall metrics volumes were unchanged. As part of the upgrade
