cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pedro Gordo (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-14865) Cascading calls to read retries, system_auth, and read repairs
Date Fri, 02 Nov 2018 11:22:00 GMT


Pedro Gordo commented on CASSANDRA-14865:

I have seen AlwaysSpeculatingReadExecutor mentioned in this comment (
I wonder if classes of the same sort apply to the other mechanisms and are being triggered.

> Cascading calls to read retries, system_auth, and read repairs
> --------------------------------------------------------------
>                 Key: CASSANDRA-14865
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Pedro Gordo
>            Priority: Major
>             Fix For: 3.11.1
>         Attachments: cn_dc.txt, nec_dc.txt, wec_dc.txt
> Roles validity and permission cache values are the default ones. Same thing for the read-repair
> We have a cluster with 3 data centers. We have noticed that in 2 of the data centers
(NEC and CN) we have multiple calls to speculative read retries (rapid read protection), roles
(instead of using cached values within the same tracing session), and multiple read repair
> We would expect calls to roles, within sequential read sessions, because the cache could
be turned, but not so many calls within the same tracing session. Same thing for read-retries,
and read repair messages. We are discarding blocking read repairs possibility because we consistently
get the same results when doing the query several times.
> It feels like something is cascading calls to these mechanisms regardless of conditions
that would prevent them from being called (cached roles values for instance).
> I have attached tracing files from the 3 data centers. Please let me know if more info
is needed.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message