[
https://issues.apache.org/jira/browse/CASSANDRA-16465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327163#comment-17327163
]
Nicolai Vest commented on CASSANDRA-16465:
------------------------------------------
I have to object. In our setup it does happen with 3.11.7. With 3.11.6
performance is still ok. The tables affected use TWCS and impact can already be
observed on our test environment with just little load (3 nodes, 15GB Data with
TTL of one week, and ~30k commit logs at the last 2 minutes).
> Increased Read Latency With Cassandra >= 3.11.7
> -----------------------------------------------
>
> Key: CASSANDRA-16465
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16465
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
> Reporter: Ahmed ELJAMI
> Priority: Normal
> Fix For: 3.11.11
>
>
> After upgrading Cassandra from 3.11.3 to 3.11.9, Cassandra read latency 99%
> increased significantly. Getting back to 3.11.3 immediately fixed the issue.
> I have observed "SStable reads" increases after upgrading to 3.11.9.
> The same behavior was observed by some other users:
> [https://www.mail-archive.com/user@cassandra.apache.org/msg61247.html]
> According to Paulo Motta's comment, this behavior may be caused by
> https://issues.apache.org/jira/browse/CASSANDRA-15690 which was introduced on
> 3.11.7 and removed an optimization that may cause a correctness issue when
> there are partition deletions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
