[ https://issues.apache.org/jira/browse/CASSANDRA-15177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16870788#comment-16870788 ]
Ben Manes commented on CASSANDRA-15177: --------------------------------------- If you implement CacheLoader, you can override asyncReload to supply the refresh future tied to a different executor. > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org