You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sam Tunnicliffe (JIRA)" <ji...@apache.org> on 2019/06/20 18:08:00 UTC
[jira] [Updated] (CASSANDRA-15177) Reloading of auth caches happens
on the calling thread
[ https://issues.apache.org/jira/browse/CASSANDRA-15177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sam Tunnicliffe updated CASSANDRA-15177:
----------------------------------------
Severity: Normal
Complexity: Normal
Discovered By: New Unit Test
Bug Category: Parent values: Degradation(12984)Level 1 values: Performance Bug/Regression(12997)
Component/s: (was: Legacy/Local Write-Read Paths)
Status: Open (was: Triage Needed)
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org