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:04:00 UTC

[jira] [Created] (CASSANDRA-15177) Reloading of auth caches happens on the calling thread

Sam Tunnicliffe created CASSANDRA-15177:
-------------------------------------------

             Summary: 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, Legacy/Local Write-Read Paths
            Reporter: Sam Tunnicliffe


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