[ https://issues.apache.org/jira/browse/CASSANDRA-16465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17332621#comment-17332621 ]
Jai Bheemsen Rao Dhanwada commented on CASSANDRA-16465: ------------------------------------------------------- Thank you [~nvest] [~AhmedElJAMI] I tried upgrading from 3.11.6 to 3.11.9 and didn't see any perf drop with my application use-case and also the cassandra-stress too. I use LCS in all my tables (system* tables uses default shipped with Cassandra). Do you mind sharing your test scenarios where you see latency, so I can make sure I am not missing anything. [~nvest] please share your finding with 3.11.10 as well, so it will be useful for me to assess which version to upgrade. > 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.x, 4.0.x > > Attachments: Screenshot from 2021-04-24 20-50-47.png > > > 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