[
https://issues.apache.org/jira/browse/CASSANDRA-18766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873600#comment-17873600
]
Brandon Williams commented on CASSANDRA-18766:
----------------------------------------------
This bug was introduced in CASSANDRA-15241 which explains why it started in
4.1.3. However, CASSANDRA-19534 happened to fix it, so no code changes are
needed, just a release. /cc [~maedhroz] since you were involved in both of
those!
I've pared down the
[dtest|https://github.com/driftx/cassandra-dtest/tree/CASSANDRA-18766] to not
run so long but still reproduce (under 2m), and confirmed it still bisects
correctly, so I think it's suitable to commit now.
I'll work on getting 4.1.6 released for this.
> high speculative retries on v4.1.3
> ----------------------------------
>
> Key: CASSANDRA-18766
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18766
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Coordination
> Reporter: Ivans Novikovs
> Assignee: Brandon Williams
> Priority: Urgent
> Fix For: 4.1.x
>
> Attachments: screenshot-1.png, screenshot-2.png, signature.asc,
> signature.asc, v4.0.png, v4.1.png
>
>
> There are up to 10+ times higher speculative retries for reads on 4.1.3
> comparing to 4.0.7 and 4.1.2 when using QUORUM and default setting of 99p.
> On 4.1.3 after upgrade I see speculative retries for up to 35% of all reads
> for specific table. Latency for reads is stable around 500 microseconds.
> java 1.8.0_382 is used
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
