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
pr
To further clarify @carl.mueller's comments above, it would appear that
both the initial jump in metrics (and subsequent drop) was app-related, not
cassandra related.
On Tue, Jun 25, 2019 at 1:45 PM Carl Mueller
wrote:
> Nevermind, it would appear once we looked further out on the metrics there
