[
https://issues.apache.org/jira/browse/CASSANDRA-15177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-15177:
----------------------------------------
Authors: Sam Tunnicliffe
Impacts: (was: None)
Test and Documentation Plan: Covered by existing python dtests
Status: Patch Available (was: Open)
I had forgotten about this, but we ought to fix it before rc. Reloading
eligible items on a thread servicing user requests can cause timeouts and
unavailables.
[patch|https://github.com/beobal/cassandra/commits/15177-trunk],
[circle|https://app.circleci.com/pipelines/github/beobal/cassandra?branch=cci%2F15177-trunk],
[ci-c.a.o|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/500]
> Reloading of auth caches happens on the calling thread
> ------------------------------------------------------
>
> Key: CASSANDRA-15177
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15177
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Authorization
> Reporter: Sam Tunnicliffe
> Priority: Normal
>
> When Guava caches were replaced by their Caffeine equivalents in
> CASSANDRA-10855, the async reloading of stale AuthCache entries was lost due
> to the use of {{MoreExecutors.directExecutor()}} to provide the delegate
> executor. Under normal conditions, we can expect these operations to be
> relatively expensive, and in failure scenarios where replicas for the auth
> data are DOWN this will greatly increase latency, so they shouldn’t be done
> on threads servicing requests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
