Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Have rls's LRU Cache rely on cleanup process to remove expired entries #10400

Merged
merged 6 commits into from Jul 21, 2023

Conversation

larry-safran
Copy link
Contributor

Fixes b/290931431

Copy link
Member

@ejona86 ejona86 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did we confirm this is the difference with other implementations?

@larry-safran larry-safran merged commit afa4d6d into grpc:master Jul 21, 2023
14 checks passed
@larry-safran
Copy link
Contributor Author

In Go they don't remove the cache entry when it is expired, so at least for that language we are now doing it the same way, though they go further and reuse the cache entry rather than replace it when they get a response for an existing key.

@larry-safran larry-safran deleted the rls_2 branch July 24, 2023 22:34
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants