[
https://issues.apache.org/jira/browse/CASSANDRA-16465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17290916#comment-17290916
]
Nicolai Vest commented on CASSANDRA-16465:
------------------------------------------
I do have some doubt if the behavior is related to CASSANDRA-15690 because the
impact on the read latency can be observed immediately after switching the
Cassandra version. No need to wait for partitions being deleted or not.
I did initially report of the problem at the Cassandra user forum and can still
reproduce the it at both of our environments, testing (less load) and
production (heavy load). During the last months I was not able to investigate
any further but being able now to provide further information if required.
> 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/[email protected]/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: [email protected]
For additional commands, e-mail: [email protected]
