[
https://issues.apache.org/jira/browse/CASSANDRA-16957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17416275#comment-17416275
]
Josh McKenzie commented on CASSANDRA-16957:
-------------------------------------------
||Item|Link||
|JDK8
tests|[Link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/81/workflows/c6369e34-434a-4b65-9669-1dbd546cfe1f]|
|JDK11
tests|[Link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/81/workflows/ecec7f98-a879-48c6-90c6-4bee0399cbe3]|
|PR|[Link|https://github.com/apache/cassandra/pull/1204]|
> Actively update auth caches in the background
> ---------------------------------------------
>
> Key: CASSANDRA-16957
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16957
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Authorization
> Reporter: Josh McKenzie
> Assignee: Josh McKenzie
> Priority: Normal
> Fix For: 4.x
>
>
> Currently the guava cache backing the various auth caches refreshes its data
> lazily; you won't get an update on cached credentials until you try and read
> them and they're expired. For the PasswordCache in particular, this not only
> gives us a window of async "serve the old while you fetch the new" which
> isn't ideal, but also causes the cache to be invalidated and thus not adding
> value / perf after expiration period (24h I believe by default).
> The expected behavior after this change is for the caches to auto-refresh
> themselves on an interval so you a) don't have stale data sitting around
> waiting to be served, and b) getting invalidated so having effectively a dead
> cache for intermittent users assuming you have the backing resources to serve
> them proactively.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
