[
https://issues.apache.org/jira/browse/CASSANDRA-16465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17331302#comment-17331302
]
Stefan Miklosovic edited comment on CASSANDRA-16465 at 4/24/21, 6:46 PM:
-------------------------------------------------------------------------
We (Instaclustr) also spotted this issue, for us I think we saw this from
3.11.8 (excluded), but we do not know yet if the cause is in 3.11.9 or 3.11.10
(we tested 3.11.10 only where we saw this but we didnt manage to test 3.11.9
yet)
was (Author: stefan.miklosovic):
We (Instaclustr) also spotted this issue, for us I think we saw this from
3.11.8 (excluded), but we do not know yet if the cause is in 3.11.9 or 3.11.10.
> 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
>
>
> 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]
