On the systems side of things, I've found that using the new BBR TCP congestion algorithm results in far better behavior in cases of low to moderate packet loss compared to any of the older strategies. It can't fix totally broken, but it takes good advantage of "usable but lossy". 0.5-2% loss would cripple the cluster, but with BBR it hardly notices.
On Mon, Dec 30, 2019, 8:28 AM Rahul Reddy <[email protected]> wrote: > Hello, > > We have our cassandra cluster running on aws and we have 2 dc’s 6 and 6 > nodes in both regions with RF=3 and cassandra version 3.11.3 . One of the > ec2 instance had issues with network issues for 9 minutes. Since it was > network issue neither ec2 was down nor cassandra down. But this caused high > coordinator latecnys(5 Seconds) and this impacted 5% of our traffic > impacted with timeouts. We have both disk_failure_policy and > commit_failure_policy set to stop. Please let me know if any work around > for this ind of issues? > > Sent from my iPhone > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
