[
https://issues.apache.org/jira/browse/CASSANDRA-16957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17438952#comment-17438952
]
Caleb Rackliffe commented on CASSANDRA-16957:
---------------------------------------------
Completed my first pass at review, leaving several minor comments in the PR. Do
we want to add any testing for the new hot-props? (i.e. Enabling and disabling
active refresh.) I wouldn't consider that a blocker for committing this, but
figured I'd mention it.
> 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]
